1 / 207

Knowledge in IS/IT processes and standards

Explore the existing IS/IT standards for system development, maintenance, software process improvement, and IT governance, including ISO15288, ISO12207, ISO27000, BS7799, IEEE1219, ISO15504, CMMI, ISO38500, COBIT, and ITIL.

atkinsonk
Download Presentation

Knowledge in IS/IT processes and standards

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. Knowledge in IS/IT processes and standards Advisor：Dr. Celeste Ng Reporters：GROUP 5 組員名單: 951610 范博鈞 951614 林岳德 951716 林聖哲 961756 林鄭皓 971706 江宗翰 971743 張凱鈞 971744 李乃昊 971748 李柏瑾 971758 黃堃嘉 971665 羅彥騏 971766 莊舜翔

  2. What are the existing IS/IT standards available for • System Development • ISO15288 & ISO12207 • System Maintenance • ISO27000 & BS7799 • Software process improvement • IEEE1219 & ISO15504 & CMMI • IT Governance • ISO38500 & COBIT & ITIL

  3. For System Development ISO/IEC 15288 Systems Engineering - System Life Cycle Processes 971766 莊舜翔

  4. ISO 15288-Introduction • The ISO/IEC 15288 is a Systems Engineering standard covering processes and life cycle stages. • Initial planning for the ISO/IEC 15288:2002(E) standard started in 1994 when the need for a common Systems Engineering process framework was recognised.

  5. ISO 15288-history • The first edition was issued on the 1st of November 2002. • In 2004 this standard was adopted as IEEE 15288. • ISO/IEC 15288 has been updated 1 February 2008 and was edited by Stuart Arnold until 2004.

  6. Prototypical Life Cycle Model

  7. Prototypical Life Cycle Model

  8. Concept Process name input output Analyze needs Identify concepts Develop solutions Identify stakeholders’ need Propose viable solutions

  9. Concept Stage Purpose & Outcomes • Concept Stage Purpose: • Assess new business opportunities • Develop preliminary systems requirements • Design viable solution • Concept Stage Outcomes: • identify new system concepts • offer new capabilities • enhance overall performance • improve life cycle costs

  10. Development control Process name input output Meet customer requirements Determine system components Design programs Fabricate programs Integrate systems Refine system requirements Build the system

  11. Development Stage Purpose & Outcomes • Development Stage Purpose: • meets acquirer performance requirements • Development Stage Outcomes • Evaluated and refined system requirements • Confirm the system meets all system requirements • Can become product • Operate order easy

  12. Production control Process name input output Meet customer requirements produce system verify and validate system Inspect and test system Complete systems engineering Project of system

  13. Production Stage Purpose & Outcomes • Production Stage Purpose: • produce or manufacture the system products • produce related supporting • Production Stage Outcomes: • Package product transfer to distribution customers

  14. Retirement control Process name input output Need inadequacy Remove the system Backup data Keep of system’s data Employ systems

  15. Retirement Stage Purpose & Outcomes • Retirement Stage Purpose:provide for • Remove of a system • Related operational • Support services • Retirement Stage Outcomes: • Remove of waste • Required system decommissioning, including disposal, refurbishing, or recycling, in accordance with applicable laws and regulations

  16. Applicability of ISO/IEC 15288 • Key business domains • Aerospace • Telecommunications • Transportation systems • Military systems • Finance and Administrative systems • Information Technology system

  17. RESOURCES: • http://www.ap233.org/ap233-public-information/reference/ISO-15288-A4.pdf • http://en.wikipedia.org/wiki/ISO_15288 • http://www.incose.org/delvalley/iso_iec_15288.pdf

  18. Q&A Thanks

  19. For System Development ISO/IEC 15288 Systems Engineering - System Life Cycle Processes 971665羅彥騏

  20. A Life Cycle Example • 1. Concept stage • 2. Development stage • 3. Production stage • 4. Utilization stage • 5. Support stage • 6. Retirement stage

  21. System life cycle stages

  22. Support Stage Purpose To provide logistics, maintenance, and support services that enable continued system operation and a sustainable service.

  23. Support Stage(1) ●The Support Stage begins with providing maintenance, logistics and other support for the system operations and use.

  24. Support Stage(2) ●This stage includes monitoring performance of the support system and services and the identification, classification, and reporting of anomalies, deficiencies, and failures of the support system and services.

  25. Support Stage(3) • Actions to be taken as a result of identified problems include maintenance and minor modification of the support system and services, major modification of the support system or services (reference Development and Production Stages).

  26. Support Stage(4) • During this stage the support system and services can evolve under different versions or configurations. • presumed that the organization has available the support which includes the support sites, facilities, equipment and tools, trained support personnel; and maintenance manuals and procedures.

  27. Support Stage Outcomes(1) 1. Trained personnel who will maintain and provide other support services. 2. Organizational interfaces with the operating and production organizations that ensure problem resolution and corrective actions. 3. Maintained system product and services and the provision of all related support services, including logistics, to the operational sites. 4. Provide product and service maintenance and correct design deficiencies.

  28. Support Stage Outcomes(2) 5. A spare parts inventory sufficient to satisfy operational availability goals. 6. Plans and decision criteria for exiting the next stage. 7. Current risks and mitigating actions identified. 8. Transition to Retirement or the next stage in the system life cycle model.

  29. Q&A Thanks

  30. For System Development ISO/IEC 12207 ISO for software Development 961756林鄭皓

  31. What is ISO/IEC 12207? Definition ISO standard for software lifecycle processes. standard that defines all the tasks required for developing and Maintaining software. Reference:http://en.wikipedia.org/wiki/ISO_12207

  32. Three primary life cycle processes • primary life cycle processes • supporting life cycle processes • organizational life cycle • processes

  33. Primary life cycle processes • Acquisition process • Supply process • Development process • Operation process • Maintenance process

  34. ISO/IEC 12207 for software Development • Project • Process implementation • Software installation • Software acceptance support • System • System requirements analysis • System architectural design • System integration • System qualification testing • Software • Software requirements analysis • Software architectural design • Software detailed design • Software coding and testing • Software integration • Software qualification testing

  35. ISO/IEC 12207 for software Development • Process implementation • Define software life cycle • model. • Select and use standards, • tools, languages. • Document development • plans. • Deliver all needed products Reference: http://www.scribd.com/doc/47225464/12207

  36. ISO/IEC 12207 for software Development • System requirements analysis • Specify system requirements. • System architectural design • Establish top-level architecture.

  37. ISO/IEC 12207 for software Development • Software requirements analysis • Document software requirements. • comprehensive description of the intended purpose and environment for software under development.

  38. ISO/IEC 12207 for software Development • Software architectural design • Transform requirements into • architecture. • Document top-level design for • interfaces. • Document top-level design for • database. • Document preliminary user • documentation. • Document preliminary test requirements.

  39. ISO/IEC 12207 for software Development • Software detailed design • Document design for each component. • Document design for interfaces. • Document design for database. • Update user documentation. • Document unit  test requirements. • Update integration test requirements.

  40. ISO/IEC 12207 for software Development • Software Construction • Software coding and testing • Document and tests each unit, • database . • Conduct and document unit • testing. • Update user documentation. • Update integration test requirements. • Evaluate code and test results

  41. ISO/IEC 12207 for software Development • Software integration • Document integration plans. • Conduct and document • integration tests. • Update user documentation. • Document qualification tests.

  42. ISO/IEC 12207 for software Development • Software qualification testing • Conduct and document qualification • testing. • Update user documentation. • Prepare product for next phase.

  43. ISO/IEC 12207 for software Development • System integration • Integrate software with hardware • & others. • Document integration tests. • System qualification testing • Conduct and document • qualification tests. • Prepare product for installation

  44. ISO/IEC 12207 for software Development • Software installation • Plan installation in target • environment. • Software acceptance support • Support acquirer's acceptance • tests. • Deliver product per contract. • Provide training per contract.

  45. Limitations • does not specify the details of how to implement or perform the activities and tasks included in the processes • does not imply that such documents be developed or packaged separately or combined in some fashion.

  46. Q&A Thanks

  47. For System Maintenance ISO/IEC 12207 ISO for System Maintenance 971748 李柏瑾

  48. A Recommended Software Maintenance Process 1.The process starts with the requirement to maintain a software product and ends with the retirement of the software product. 2.The requirement to maintain software should be included in a system’s specification and may include very specific language with warrantees, maximum time to fix, penalties for bad bug, life cycle description for migration to new version of operating system and hardware within certain time periods. 3.An organization structure must be establish to fix problems, adapt software to new environments, and implement enhancements. 4.Maintenance must be considered as a normal part of a software lifecycle.

  49. The ISO/EIC 12207 Maintenance Process Purpose is to establish a process that is controllable. This helps 1.reduce effort, 2.improve quality, 3.reduce risks , 4.keep customers happier. Customer and maintainers each have responsibilities.

  50. The ISO/EIC 12207 Maintenance Process EXAMPLE: Inputs: required inputs into an activity Controls: provides controls (checks and evaluations) of an activity Support: items that support an activity like defined processes or metric collections Outputs: outputs from an activity

More Related