<Enter team name here>
<Enter project name here>
Software Tools
Version <1.0>
<Date>
2010<Enter team name here> / <Drive:\Directory\Filename.ext>Software Tools Report
Document Control
Approval
The Guidance Team and the Customer shall approve this document.
Document Change Control
Initial Release:Current Release:
Indicator of Last Page in Document:
Date of Last Review:
Date of Next Review:
Target Date for Next Update:
Distribution List
This following list of people shall receive a copy of this document every time a new version of this document becomes available:
Guidance Team Members:
Dr. Steve Roach
Clients: < client>
Software Team Members: <Your Names Here>
Change Summary
The following table details changes made between versions of this document
Version / Date / Modifier / DescriptionTable of Contents
Document Control
Approval
Document Change Control
Distribution List
Change Summary
1. Introduction
1.1.Purpose of the Tools Report
1.2.Project Description
1.2.1.Use Case Diagram
1.2.2.Actors
1.2.3.Use Case Descriptions
1.3.User Interface Description
1.4.Justification for the Proposed System
1.5.Considerations
2.Existing Systems and Technologies
2.1.<First Item>
2.1.1.Option 1
2.1.2.Option 2 … Option n
2.2.< Second Item>
2.2.1.Option 1
2.2.2.Option 2 … Option n
3.Solutions
3.1.Solution 1
3.1.1.Resources Needed
3.1.2.Limitations
3.2.Solution 2
3.2.1.Resources Needed
3.2.2.Limitations
3.3.Solution 3
3.3.1.Resources Needed
3.3.2.Limitations
4.Risks and Cost Estimates
4.1.Risks and risk mitigations
4.2.Schedule and Cost Estimates
5.Comparison of Solutions
6.Conclusions
7.References
Software Tools Report / <Enter team name here> / Date11/2/20185:44 PM / Page
1
Software Tools Report
1. Introduction
< BEFORE YOU BEGIN:
This outline is structured in sections. To display section breaks, headers and footers, from the View menu, point to Page Layout. To add information to a chapter, insert the information before a section break to ensure it flows onto the next page properly. Information inserted after a section break disrupts the header and footer layout scheme and results in incorrect pagination. For more information about section breaks, consult Microsoft Word’s online help. >
1.1.Purpose of the Tools Report
< The purpose of this document is to … >
1.2.Project Description
Provide an overview of project. You should summarize the purpose of the proposed software and any of the requirements that impact the use of COTS or third-party software. This should describe the use cases (user stories) and the actors.
1.2.1.Use Case Diagram
1.2.2.Actors
< List all actors and describe each. >
1.2.3.Use Case Descriptions
Describe the main use cases of the system. It is unlikely at this point that you will know enough to write complete scenarios. >
1.3.User Interface Description
To the extent possible, describe the desired user interface.
1.4.Justification for the Proposed System
< provide a business case for the system. What will the benefits of the system be? Who will benefit? >
1.5.Considerations
This section establishes the criteria upon which you will evaluate possible solutions. You must identify the primary concerns related to this project. You need to decide what aspects of the system are most important. Is performance something to worry about? Is usability the driving factor? Is security something for which you must plan? What features in the system matter most?>
2.Existing Systems and Technologies
< This section will describe systems and technologies that either achieve a solution or can be used to achieve a solution. You should describe any prototype or production system that is in place, commercial and off-the-shelf software that can be used, and open source software that might apply. Your descriptions should include software that you might use to create a solution. For example, if you require data management, you will need to discuss database management systems. If the system requires interactive graphics, you should discuss graphics packages that can be used. You should find at least two (preferably three) examples of each type of software.
Do not include discussions of general purpose, mainstream programming languages such as Java or C++. >
2.1.<First Item>
< In this section, describe existing systems that achieve or partially achieve the goals of the proposed system. Use the headings and titles as appropriate.
2.1.1.Option 1
2.1.2.Option 2 … Option n
2.2.< Second Item>
2.2.1.Option 1
2.2.2.Option 2 … Option n
3.Solutions
< Describe possible solutions. Each solution should be complete in the sense that it will fully achieve the goals of the proposed system. If your solution includes existing software, it must be described in Section 2.You must provide at least three solutions.
3.1.Solution 1
< Describe the solution.>
3.1.1.Resources Needed
< Include software, hardware, and training.
3.1.2.Limitations
< If the solution does not meet all of the goals or if modifications to exiting software or hardware are needed, describe these. >
3.2.Solution 2
< Describe the solution.>
3.2.1.Resources Needed
< Include software, hardware, and training. >
3.2.2.Limitations
< If the solution does not meet all of the goals or if modifications to exiting software or hardware are needed, describe these. >
3.3.Solution 3
< Describe the solution.>
3.3.1.Resources Needed
< Include software, hardware, and training. >
3.3.2.Limitations
< If the solution does not meet all of the goals or if modifications to exiting software or hardware are needed, describe these. >
4.Risks and Cost Estimates
4.1.Risks and risk mitigations
< identify risks to the completion of the system. Possible risks include technical infeasibility as well as time-to-market risks. For each risk, identify possible mitigations. >
4.2.Schedule and Cost Estimates
< Provide a brief production schedule and initial cost estimates, if possible. >
5.Comparison of Solutions
This section should discuss how each option measures up against the considerations described in Section 4 and how each compares with the others.
You may choose to include some of the following:
• Specific hardware and software requirements
• Time constraints
• Ease of use
• Staffing levels and training required
• User preference
• Security issues
A matrix that compares features is required.
6.Conclusions
Summary and recommendations >
7.References
All information in the above text that comes from outside sources should be cited. All references that are cited should be enumerated below. Use IEEE citation style.
Software Tools Report / <Enter team name here> / Date11/2/20185:44 PM / Page
1