1 / 19

ICSM

ICSM. CS 577b Software Engineering II Supannika Koolmanojwong February 11, 2011. Challenges about ICSM from HW1 ??. Does not fit with agile approach Does not scale up, not good for system of systems Does not cover COTS mismatch, COTS reuse, Legacy SW Lack of mentioning about glue code

knut
Download Presentation

ICSM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ICSM CS 577b Software Engineering II Supannika Koolmanojwong February 11, 2011

  2. Challenges about ICSM from HW1 ?? • Does not fit with agile approach • Does not scale up, not good for system of systems • Does not cover COTS mismatch, COTS reuse, Legacy SW • Lack of mentioning about glue code • Can not handle systems with high security • Difficulties with scalability and usability by less experienced programmers (C) 2011 USC-CSSE

  3. ICSM common cases

  4. ICSM common cases (new)

  5. (C) 2011 USC-CSSE

  6. Challenges about ICSM from HW1 ?? • Sequential milestones of the development • The activities in ICSM are not synchronized • Workload is not divided equally at each phase • Difficult to define objectives of each milestone • Document Tailoring • Excessive time spent on project planning and risk management (C) 2011 USC-CSSE

  7. The Incremental Commitment Spiral Model 6 Key Principles: Commitment and accountability Incremental growth of system definition and stakeholder commitment Concurrent engineering and Iterative development cycles Success-critical stakeholder satisficing Risk-based activity levels and milestones

  8. (C) 2011 USC-CSSE

  9. ARB Review Success Criteria 4

  10. Challenges about ICSM from HW1 ?? • For NDI-intensive projects, all risk analysis must be done before it is incorporated into the system • Risk assessment expertise is required and the model is complex • Response from V&V need to be replied to by the development team or defer to a later increment, this keeps piling on works on later increments (C) 2011 USC-CSSE

  11. Challenges about ICSM from HW1 ?? • Lack of value-based components • Does not solve the problem of needing pre-specified requirements since too much rework would be needed to take place if requirements change drastically (C) 2011 USC-CSSE

  12. Common mistakes about a role and responsibilities of a systems engineer for 577ab (C) 2011 USC-CSSE

  13. Forgot that this is a systems engineer for 577ab • Assign current responsibilities to the systems engineer • Overlapping of responsibilities • Overlapping of documentations • Need further clarification • Primary / additional performer • Different scope on the same task ? • Various works are defined in Operations phase (C) 2011 USC-CSSE

  14. Forgot that this is a systems engineer for 577ab • Assign too much work for 577ab scope • performance analysis, interface monitoring, failure analysis, logistics analysis, tracking, and management • Heavy documentation • System quality report • System resources allocation report • System transition report • System evaluation report • Interface requirements document • Interface control document • Interface definition document • Technical data management procedures (C) 2011 USC-CSSE

  15. Responsibilities of a 577ab systems engineer(Exploration phase) (C) 2011 USC-CSSE

  16. Responsibilities of a 577ab systems engineer(Valuation phase) (C) 2011 USC-CSSE

  17. Responsibilities of a 577ab systems engineer(Foundations phase) (C) 2011 USC-CSSE

  18. Responsibilities of a 577ab systems engineer(Development phase) (C) 2011 USC-CSSE

  19. Responsibilities of a 577ab systems engineer(Operations phase) (C) 2011 USC-CSSE

More Related