There will be two deliverables associated with the Systems Engineering Project: a Proposal, which may be submitted as early as the term in which the last academic course prior to SYSE 697 is being taken, but not later than the end of the first week of SYSE 697; and the final Systems Engineering Project document. The final Project will be due at the end of the term for SYSE 697, along with the advisor-signed checklist in the Attachment. Content of the two deliverables is outlined below.
1. Title of the project
2. General description of the project (1 page)
3. Description of how the project is systems engineering related
4. Project Journal of 4 key events, covering the concept phase of the project, which:
a) Identifies When the Events will occur
b) Identifies How the Events will be performed and Who will be involved
c) Briefly Identifies Why the Events are needed and will be performed
FINAL PROJECT CONTENT
1. Title of the Project
2. General assumptions that are associated with this project (up to 1 page)
3. The strategic importance of the project (up to 4 pages)
a) Project value for the customer: direct benefits; indirect benefits
b) Project value for the entity executing the project: direct benefits; indirect benefits.
4. Systems Engineering Management Plan, containing as a minimum:
A. Project Statement of Work (1-2 pages). Describe:
a) Who is going to execute the project?
b) Who is the project customer?
c) What are the general objectives of the project?
d) What are the tangible outputs?
e) What is the funding source?
f) What is the funding amount? (known or estimated)
g) Brief description of project tasks
h) Brief description of project tangible outputs
i) Start date
j) End date
k) What will be provided by the entity executing the project?
l) What will be provided by the project customer?
B. Work Breakdown Structure (up to 2 pages). Use indented or graphic format. Show the major elements of the project up to the lowest level of activity package and activities.
C. Summary of Technical Specifications (up to 1 page)
D. Engineering Specialties Identification and Integration Plan
E. Risk Management Plan, as follows:
a) Identify 4 risks that can put the project performance and capabilities in jeopardy
b) Create a table that assigns probability values to these 4 risks depending on the project characteristics. For example, if cold weather is a risk a scale can be defined as: Low probability (0.1) if project is performed in summer, Medium probability if it is performed in spring or fall (0.5), and high probability if it is performed in winter (0.9).
c) Using the table identify the probability of each of the 4 risks depending on the characteristics of the project. For example, if performed in fall the probability is equal to 0.9 (90%)
d) Identify 3 areas that are critical for the performance of the project. For example, cost performance, schedule performance, quality performance.
e) Create a table that assigns consequence or impact values to the 4 areas of performance. For example, a large impact upon the cost performance of a project can be defined as (0.9) if the budget is exceeded in more than 50%, a medium impact is if the budget is exceeded more than 10% and less than 50%, a low impact is if the budget is exceeded in less than 10%.
f) Identify the level of impact that each of the 4 risk identified in 10.a) will have in each of the 3 areas that are critical for the performance of the project.
g) Calculate the severity of each risk and rank them in terms of severity
h) Identify the strategy for dealing with each risks
i) Identify at least one indicator(s) to track each risk
j) Calculate the overall Project Risk Factor and using the rule of thumb provided in the power point presentation, determine if it is a high, medium, or low risk project
5. Stakeholder analysis of at least four key stakeholders. Complete a Table 1 and Table 2 for each stakeholder with the following information:
Table 1-Stakeholder Analysis
• How the stakeholder’s interests are aligned with the interests of the project
• How, formally, the stakeholder is linked to the project (customer, user, etc.)
• What power the stakeholder exerts over project execution and deliverables
• How stakeholder past performance is important for the stakeholder management process
Table 2-Stakeholder Analysis
• An approach to deal with the alignment or any misalignment
• How the approach will be implemented (at a general level of detail)
• How the satisfaction of the stakeholder will be measured
6. Analysis of the schedule for a network of 15 interrelated activities
A. 15 +/- 3 Activities (lowest level of the WBS)
B. Pessimistic, optimistic, and most likely time of each activity
C. What activities precede each activity (predecessors)
D. PERT CHART, showing critical path (up to 3 pages). It can be performed using MS-Project, MS-Visio, or any other drawing tool.
E. Probability of completing the project by the time set by the customer (state any assumption) (1/2 page)
F. GANTT CHART (1 page). It can be performed using MS-Project, MS-Visio, or any other drawing tool.
7. Resource Loading Chart and Discussion (up to 3 pages)
A. Identify the level of detail that will be used to plan and control the project. For example days, weeks, months, quarters.
B. Identify at least 3 resources needed per each activity.
C. Identify the unit in which the consumption of these resources are measured
D. Identify the amount of resources needed per activity per unit of time identified in 7.A (for example, number of hours that an engineer needs to work in a given activity every week).
D. Build the resources loading chart
8. Responsibility Matrix and Discussion (up to 3 pages)
A. Identify 5 key stakeholders that will be assigned responsibilities during the duration of the project
B. Identify the type of responsibilities that will be assigned to each of the 5 stakeholders in each of the 20 +/- 3 activities that are going to be executed in the project. For example, (N) needs to be notified, (MG) managerial responsibility, (A) approval required, etc.
C. Build the responsibility matrix
9. List and provide details regarding four Critical Knowledges (or knowledge areas) for the project. Use a table for each critical knowledge with the following input:
A. Explanation of why the knowledge is critical
B. At least one source of each critical knowledge
C. The knowledge transfer method to be used (if there is a source).
D. The knowledge creation method to be used (if there is not a source).
10. Communication management of 4 key project communications, which must include project reporting. Use a table for each project communications with the following input:
A. Sources of communication
B. Recipient of communication
C. Purpose of the communication
D. Information and data needed in the message
E. Frequency of the message
F. Feedback required
G. Title of the communication action
11. A Project Budget that is Time-Phased and WBS-based, and a discussion of it
A. Use the resources loading chart to determine the amount of resources needed per each activity per unit of time as defined in the loading chart
B. Identify a cost per unit per each of the resources
C. Identify a percentage of cost overhead that will be applied to the calculation of the costs
D. Build the time-phased budget showing totals per activity, per unit of time, per resource, and for the whole project
12. Project Journal of 10-15 key events:
• The Final Project Journal is where the student relates the activities to components of systems engineering to your decision-making.
• It documents the major decisions students are making as they develop the system.
o It is used as a way of documenting those decisions and why the decision was made.
• It gives the instructor insight as to why the student made some of the twists and turns in the development of the SEMP.
• It provides a means, if students made a poor decision in system development, to go back to the reasons they made said decision and to retrace and go down a different development path.
Instructions for the student:
• As you make the major decisions in the analysis and development of the system make entries into the journal.
• In your entry describe the event/decision including the time of the event, details of the event/decision, who or what is affected by the decision and what decision was made.
• Refer to the journal whenever it is necessary to determine a change in direction or confirmation of a plan of action.