Question 1 This question concems the system engineering lifecycle (a) The follow
ID: 420609 • Letter: Q
Question
Question 1 This question concems the system engineering lifecycle (a) The following diagram (Figure 1.1) shows a project lifecycle model integrated with a system engineering model. Describe the key features with particular emphasis on design integration. 5 marks] Customer Whole Product View Customer Systen Intertace Man Technical Performance Syem Management and Design Analysis Co-ordination Inmegration Top-down Design Sub-ekment Sub-element build Validation Validation ?nd Integration Design Definition -Virtual Build Complete Produet or Syatem System Sub Systems FCAAreas Equipment compiete Design & Installed System--__ Physical areas Figure 1.1l (b) Descibe how such a model may be developed into an integrated project planning (c) Descibe the 'left-hand' and 'right-hand' planning process emphasizing any planning (d) How does the design lifecycle relate to the project management lifecycle? process. [5 marks] contradictions [5 marks] [5 marks]Explanation / Answer
Answer(a) The focus of the model is to illustrate how requirement gathering focus of system engineering can help in improving the project management practices.The project lifecycle V model includes te development of program vision, business blueprint ,gap analysis for As-is and To-be processes/states,transfrmation outcomes, plans and capability statements. This boils down to the project level plans and outcomes. From System engineering perspective the key concepts illustrated are requirement gathering,operational context, validation system to validate and test ,mapping of system requirements to verification tests and output a verified system, The verification tests would conform to system requirements and validation tests would conform to user requirements.The integrated model combines and complements the perspectives of both the project management and system engineering lifecycle models .In the integrated model the user requirements capture the business needs, constraints and compares it with the operational capabilities for high and low level design as per feasibility considerations. The validated system supports the user requirements. The capability elements define what are the deliverables and scope of the project.The blueprint integrates the capability elements to deifne how a varified system would look like.this is turn results in system requirement design and architecture which defines how the designed system should behave
Answer (b)Integrated project management is based on the following tenets:
-Project charter, project scope, project management plan,project execution, monitoring and control.
The model can be extended to act as an integrated project management planning tool in the following way:
-define project tasts:Needs, utilities, goals, objectives
-identify stakeholders: usage ,ownership, contribution, approval,acceptance
-identifying resources: Material, finances, plants/facilities, skillsets,capabilities
-Project execution: Schedule, master planning, KPIs, monitoring , Collaboration
-Managing project micro and macro environment:Technology, interface, regulatory environment, legal framework
Answer (c) The right side of the V-model is marked by the gathering of user requirements. THis is extrmely crucial as the better is the understanding ofthe requirement,the more stable will be the development phase/cycle. Next product interface mock up/wireframe are prepared whcih acts a a proxy as to how an interface would look like.The functional specifications design (FSD ) are defined in details whcih provide description about all the system functionalities. The right side is more focussed on product/project defination phase and each of the features needs validation by the customer/end-user.
The left side of the model represents development followed by system integration, tests(system integration, unit test,regression tests) and verification by QA in order to detect and correct bugs(if any). The user acceptance testing is carried out by SMEs and business users to verify of the desiged system behaves as per the user requirements. This is done by testing multiple end to end business scenarios as close as possible to reality. Upon validation the user training is conducted and system handover is carried out. Provisions are also kept for system maintenance and upgradation.
The planning contradictions are more evident for agile project lifecycle management and lacks coherence and consistency.It does not efficiently support change management practices
Answer ( d): Design lifecycle can be split into architectural or high level design and detailed or low level design. High level design encompasses system architecture and high level representation of the decomposition of the system elaborating the relationships and flows between the various entitites and their corresponding attributes. It comprises of platforms, products, services,processes etc.The low level design will contain detailed functional design ,interface details, dependencies , error listings etc.It gives the internal logic of developing the product
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.