1 / 17

Assessment Plan for Advanced GUI Ltd .

Assessment Plan for Advanced GUI Ltd. 1. General 1.1 Objectives. This plan provides the basis for an initial capability determination for Advance GUI Ltd . Up to an including capability level 3 under a SPICE V2 Assessment. Assessment Plan for Advanced GUI Ltd. 1.2 Background.

fala
Download Presentation

Assessment Plan for Advanced GUI Ltd .

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. Assessment PlanforAdvanced GUI Ltd. 1. General 1.1 Objectives. This plan provides the basis for an initial capability determination for Advance GUI Ltd. Up to an including capability level 3 under a SPICE V2 Assessment Assessment Case Study - slide#1

  2. Assessment Plan for Advanced GUI Ltd. 1.2 Background This second-party assessment by Avra Software will determine the capability of Advanced GUI Ltd.in its Engineering practices, based on the SPICE V2 model (published in May 6, 1996). The scope of the assessment will only include process ENG.2 (Develop Software Requirements). 1.3 Acknowledgement This plan is based on one used for the assessment of NewCo developed by Amr Kamel on Oct. 22, 1996. 1.4 References • SPICE - Part 5: An assessment model and indicator guidance. Assessment Case Study - slide#2

  3. Assessment Plan for Advanced GUI Ltd. 2. Assessment Inputs 2.1 Assessment Purpose To perform a capability determination of Advanced GUI Ltd in its Engineering process, based on the SPICE V2 model (published in May 6, 1996). 2.2 Assessment Scope 2.2.1 Processes The assessment will assess the process ENG 2 “Develop Software Requirements” up to and including level 3. 2.2.2 Organizational Unit See description in Section 2.2 of the case study Assessment Case Study - slide#3

  4. Size Location Experience Size Criticality Complexity App. Domain Technology Reliability Portability Efficiency Usability Maintainability Assessment Plan for Advanced GUI Ltd. 2.2.3 Target Characteristics The organizational characteristics are: Small (25 software experts) Imaginville, Saskatchewan 12 year old company The product characteristics are: medium ? moderate medium GUI. financial sw components mandatory desirable desirable GUI builders mandatory Assessment Case Study - slide#4

  5. Lifecycle Method Language Environment Assessment Plan for Advanced GUI Ltd. The process characteristics are: unknown Evolutionary component dev. unknown PC-based 2.3 Assessment Constraints Assessment is based on a brief case study description plus instructor’s interpretation. Only one instance of the process is assessed. 3. Assessment Outputs 3.1 Deliverables i) Process profiles, ii) Assessment context, iii) Assessment final report Assessment Case Study - slide#5

  6. Assessment Plan for Advanced GUI Ltd. 4. Assessment Team Roles and Responsibilities 4.1 Assessment Team Leader Mr. Paolo Ferrari, ESI Assessor -- duties as on page 3 4.2 Qualified Assessors Paul Sorenson (ISO 9001 trained), Amr Kamel (SPICE trained) -- duties as on page 3. 5. Project Controls 5.1 Document Controls All documents become the property of Advanced GUI Ltd. 5.2 Risk Management No participants will be interviewed from engineering staff Assessment Case Study - slide#6

  7. Assessment Plan for Advanced GUI Ltd. 6.`Quality Plan - 6.1 Quality Criteria review page 4 As on page 4 6.2 Quality Method The assessment will follow the Assessment Model defined in Part 5 of the SPICE 2 document. 6.2.1 Assessment Team Meetings As on page 5 7. Key Activities 7.1 Assessment Initiation As on page 5 -- replace with today’s date and in-class initiation meeting. Assessment Case Study - slide#7

  8. Assessment Plan for Advanced GUI Ltd. 7.2 Process Instance Selection For ENG 2 (Develop Software Requirements). Sample size is limited to one instance. 7.3 Assessment Preparation 7.3.1 Assessment team preparation Assessors (instructors) prepared for this class through training courses, doing assessments and reviewing SPICE materials 7.3.2 Assessment Planning Jan.7, 1996, Ferrari visited Advanced GUI to explain the SPICE Assessment process. Outline for this Assessment Plan has been developed by Paul Sorenson and Amr Kamel and submitted for the class for review. Assessment Case Study - slide#8

  9. Assessment Plan for Advanced GUI Ltd. 7.3.3. Organizational Unit Briefing Taking place now -- should include the items given on page 6 in NewCo example. 7.3.4 Assessment Techniques As on page 6. 7.3.5 Assessment Instrument Checklists will be developed. 7.3.6 Facilities We will use this room as a meeting and interview room. 7.3.7 Participant Selection Similar to what’s given on page 6. Assessment Case Study - slide#9

  10. Assessment Plan for Advanced GUI Ltd. 7.3.8 Supporting Documentation Only the case study description and dialog are available 7.4 Information Gathering Information will be gathered by reviewing the case study description and dialog. 7.5 Determining and Validating Ratings Rating determination will be as described in Part 5 of SPICE V2. No validation is possible. 7.6 Assessment Output The detailed findings will include consolidated ratings, identified risks, and proposed action plan. Assessment Case Study - slide#10

  11. Assessment Plan for Advanced GUI Ltd. 7.7 Follow-up As on page 7 8. Schedule Activity Time Assessors Process addressed Checklist developmt. Now Paul&Amr ENG2. Checklist developmt Next All ENG5.,SUP1.,MAN1 Interview N+30 Team1 ENG5. Interview N+45 Team2 SUP1. Interview N+60 Team3 MAN1. 9. Version Version 1.0, May 22, 1998 Assessment Case Study - slide#11

  12. ENG.2 Develop Software RequirementsChecklist The purpose of the Development software requirements process is to establish the requirements of the software components of the system. As a result of successful implementation of the process: • the requirements allocated to software components of the system and their interfaces will be defined to match the customer’s stated and implied needs; • analyzed, correct and testable software requirements will be developed • the impact of software requirements on the operating environment will be understood Assessment Case Study - slide#12

  13. ENG.2 Checklist (continued) • a relevant software release strategy will be developed that defines the priority for implementing software requirements; • the software requirements will be approved and updated as needed; • the software requirements will be communicated to all affected parties 1. What is your strategy for determining and analyzing requirements of the software components of the system? 2. How do you document these requirements? 3. How do you determine the interfaces between the software requirements and other components of the operating environment? Assessment Case Study - slide#13

  14. ENG.2 Checklist (continued) 4. What is your method of communicating the software requirements to the customer? How are revisions to requirements handled? 5. How do you prioritize software requirements and map them to future releases? 6. How do you use preliminary or prototypical versions of the system to affect the next iteration of requirements? 7. How and to whom do you disseminate software requirements and software requirement updates? Assessment Case Study - slide#14

  15. Input 52) Customer requirements 52) Maintenance requirements 44) Product needs assessments 83) Customer request 94) Change request 53) System design/architecture 84) Problem reports 87) Communication mechanisms 101) Database design Output 52) Software requirements 21) Analysis results ENG.2 Associated Work Products Assessment Case Study - slide#15

  16. Generic Process Assessment PA 2.1 Performance Management 1. How do you identify the resource requirements needed to capture and update software requirements? 2. Show me a plan for the performance of requirements analysis that identified the activities to be undertaken the resources involved. 3. Show me how this plan is effective. 4. How are the planned requirements activities managed so that they remain within stated time and resource requirements? Assessment Case Study - slide#16

  17. Generic Process Assessment (cont.) PA 2.2 Work Product Management 1. What procedures and checks do you have in place to ensure the quality and integrity of your system requirements documents? 2. How do you manage different versions of the requirements documents and other requirement work products to ensure their integrity? 3. How do you manage the quality of the requirements documents and associated work products? In particular, how and by whom are they reviewed? Assessment Case Study - slide#17

More Related