COMP 7881讲解、辅导Software编程、c/c++，Java程序语言辅导 辅导留学生 Statistics统计、回归、迭代|讲解SPSS
- 首页 >> Matlab编程 COMP 7881 – Advanced Topics in Software Engineering
Term Project: Create an integrated DevOps
Tool Chain
Instructor: Dr. Abhijit Sen
“It is an immutable law in business that words are words, explanations are
explanations, promises are promises- but only performance is reality.”
Harold S. Green
1. Description of the Project: To be done individually
This course includes a required technical term project. There are number
of software tools available in the market for performing DevOps
functionalities. Tool chains provide an integrated set of tools to build,
deploy and manage your apps. You can create tool chains that include
customized services, open source tools, and third party tools that make
development and operations repeatable and easier to manage. The purpose
of this project is to create a set of tools that can be used to cover DevOps
Life cycle. There are many models of DevOps Life cycle. Select one model
of DevOps Life cycle, prepare a tool chain for the selected DevOps Life
cycle model. Create a scenario of a possible simple project. Investigate
each tool in the tool set and prepare a formal report on suggested tool chain
that that can be used in your scenario project. The tools must be current,
and you should look at both simple to advanced tools available for
Windows and UNIX based systems. You must in your report give
evidence that you have tried each tool in the tool set. Students have
freedom to choose the types of tools to be used and approach for studying
them. It is expected that all term projects will require some amount of
additional research and reading. You may want to make use of tools that
you have experimented for your assignments.
Page 2 of 4
2. Submission Requirements:
Your final report must be professionally written, technical and precise.
Avoid verbosity. You will be graded on the content and the
presentation, but not on the length of the document. The paper should
be written in your own words. All sources consulted should be
explicitly cited. Bibliographic entries should be complete. Direct
quotation should only be used when appropriate. All direct quotations
should be clearly identified in the text.
Your report should normally have the following logical components;
the keyword is logical -- physical organization of the paper can again
vary enormously depending on personal style and nature of the topic
but can still have the logical components.
a. Introduction: The description of the application you are going to
develop (what & why), how it is related to DevOps in general, aim
and scope and nature of the present study.
b. Basic Terminology and existing literature: Do not try to define
everything -- you'll define only those things that are important for
understanding the subsequent material and that are not expected of
any COMP 7881 student.
c. DevOps model used – state name of the stages with brief
description, relate the stage to your project
d. For each tool create a table that include the following:
Column Title Contents
Name Name of the tools
Website Vendor name and website where the tool is available,
include resource sites as well.
Version The current version available (include betas, if
appropriate)
DevOps Stage Describe the tool which is used at what stage (such as
build, monitoring …) and the purpose
Page 3 of 4
Requirements/
Compatibility
List any hardware or software requirements, as well as
compatibility issues – also include issues that you
encounter in using the tool
e. Main Results: Depending on what you have done (use as many
subsections as you wish. For each experiment with tools include the
following:
Purpose of the experiment with tools at different stage
Test Environment (Hardware/Software)
o Hardware Configuration
o Operating System
o Software tools used
Step by step procedures of the experiment with tools
Experimental results (with screen shots)
Analysis of the result
f. Conclusion: Give a summary, highlight the main points of your
study, and discuss limitations and further work that can be done.
g. References: Be as complete as you can
h. Name the word file as :
Project_ Lastnames_Initials.doc
3. Marking Scheme
Marks will be based on the following
Project Marks: 100 Marks
Quality and complexity and currency of Tools: 20 marks
Number of tools used for each stage: 10 marks
Demonstration of tools in your project scenario: 30 marks
Demonstration of tools using multiple O/S 15 marks
Quality, and content of Report: 25 marks
Page 4 of 4
4. Notes to Remember
a. The report must have a cover page as specified in section 3
b. The report must have a proper table of contents
c. Each section and subsection must have section and subsection
numbers with proper heading.
d. Each screenshot or Tables must have Figure or Table numbers
with proper captions.
e. Each page except the first page must have proper page numbers
in the bottom center of the pages.
f. The report must be a formal report written in 3rd person.
Term Project: Create an integrated DevOps
Tool Chain
Instructor: Dr. Abhijit Sen
“It is an immutable law in business that words are words, explanations are
explanations, promises are promises- but only performance is reality.”
Harold S. Green
1. Description of the Project: To be done individually
This course includes a required technical term project. There are number
of software tools available in the market for performing DevOps
functionalities. Tool chains provide an integrated set of tools to build,
deploy and manage your apps. You can create tool chains that include
customized services, open source tools, and third party tools that make
development and operations repeatable and easier to manage. The purpose
of this project is to create a set of tools that can be used to cover DevOps
Life cycle. There are many models of DevOps Life cycle. Select one model
of DevOps Life cycle, prepare a tool chain for the selected DevOps Life
cycle model. Create a scenario of a possible simple project. Investigate
each tool in the tool set and prepare a formal report on suggested tool chain
that that can be used in your scenario project. The tools must be current,
and you should look at both simple to advanced tools available for
Windows and UNIX based systems. You must in your report give
evidence that you have tried each tool in the tool set. Students have
freedom to choose the types of tools to be used and approach for studying
them. It is expected that all term projects will require some amount of
additional research and reading. You may want to make use of tools that
you have experimented for your assignments.
Page 2 of 4
2. Submission Requirements:
Your final report must be professionally written, technical and precise.
Avoid verbosity. You will be graded on the content and the
presentation, but not on the length of the document. The paper should
be written in your own words. All sources consulted should be
explicitly cited. Bibliographic entries should be complete. Direct
quotation should only be used when appropriate. All direct quotations
should be clearly identified in the text.
Your report should normally have the following logical components;
the keyword is logical -- physical organization of the paper can again
vary enormously depending on personal style and nature of the topic
but can still have the logical components.
a. Introduction: The description of the application you are going to
develop (what & why), how it is related to DevOps in general, aim
and scope and nature of the present study.
b. Basic Terminology and existing literature: Do not try to define
everything -- you'll define only those things that are important for
understanding the subsequent material and that are not expected of
any COMP 7881 student.
c. DevOps model used – state name of the stages with brief
description, relate the stage to your project
d. For each tool create a table that include the following:
Column Title Contents
Name Name of the tools
Website Vendor name and website where the tool is available,
include resource sites as well.
Version The current version available (include betas, if
appropriate)
DevOps Stage Describe the tool which is used at what stage (such as
build, monitoring …) and the purpose
Page 3 of 4
Requirements/
Compatibility
List any hardware or software requirements, as well as
compatibility issues – also include issues that you
encounter in using the tool
e. Main Results: Depending on what you have done (use as many
subsections as you wish. For each experiment with tools include the
following:
Purpose of the experiment with tools at different stage
Test Environment (Hardware/Software)
o Hardware Configuration
o Operating System
o Software tools used
Step by step procedures of the experiment with tools
Experimental results (with screen shots)
Analysis of the result
f. Conclusion: Give a summary, highlight the main points of your
study, and discuss limitations and further work that can be done.
g. References: Be as complete as you can
h. Name the word file as :
Project_ Lastnames_Initials.doc
3. Marking Scheme
Marks will be based on the following
Project Marks: 100 Marks
Quality and complexity and currency of Tools: 20 marks
Number of tools used for each stage: 10 marks
Demonstration of tools in your project scenario: 30 marks
Demonstration of tools using multiple O/S 15 marks
Quality, and content of Report: 25 marks
Page 4 of 4
4. Notes to Remember
a. The report must have a cover page as specified in section 3
b. The report must have a proper table of contents
c. Each section and subsection must have section and subsection
numbers with proper heading.
d. Each screenshot or Tables must have Figure or Table numbers
with proper captions.
e. Each page except the first page must have proper page numbers
in the bottom center of the pages.
f. The report must be a formal report written in 3rd person.