Explore the types of work products relevant to assessment of Essay

Explore the types of work products relevant to assessment of Capability Level 2 in the Software Requirements Analysis Process - Essay Example In the capability dimension, six capability levels and nine corresponding process attributes are defined. These are presented in Table 2.1. The measurement for all process attributes is done on a four-point scale. The process dimension of this framework classifies the processes into Process categories and groups. Software Requirements Analysis is a part of the Software Implementation Process (DEV) within Software Life cycle Processes. Table 2.1: ISO/IEC 15504 – Process Capability Levels & Process Attributes Level Number Level Name Process Attribute Number Process Attribute Name 0 Incomplete Process - - 1 Performed Process 1.1 Process Performance 2 Managed Process 2.1 Performance Management 2.2 Work Product Management 3 Established Process 3.1 Process Definition 3.2 Process Deployment 4 Predictable Process 4.1 Process Measurement 4.2 Process Control 5 Optimizing Process 5.1 Process Innovation 5.2 Process Optimization 3. Software Requirements Analysis Process – Purpose & Outcomes The purpose of this process is to identify and establish the requirements for the software elements of the system. As an outcome of successful implementation of this process the accuracy and testability of software requirements is established. It is made sure that the software requirements are consistent and in line with system requirements. The priorities of the requirements are established and their impact on cost and effort estimates is analyzed (ISO/IEC FDAM 15504-5: 2011, p.72). 4. Basic work products for Software Requirements Analysis Process This section details the work products required for Software Requirements Analysis Process, their justification, characteristics and outcomes (ISO/IEC FDAM 15504-5: 2011, ISO/IEC 15504-2:2003). I. Contract Contract implies an agreement between two parties (internal or external to the organization) regarding the scope of deliverables, time required to deliver them, statutory considerations, cost of delivery, service level agreemen ts, performance evaluation criteria, review and approval procedure. A contract is required for software requirements analysis process so that the scope of the requirements to be identified is frozen to prevent any issues later. Contract is the most important document for ant stage or project and is also referred as SOW (Statement of Work) in some cases. As an outcome of this work product, the organization would be to chart its project plans. II. User Documentation User documentation is in fact required at every stage of software development process. But it is very critical for Software Requirements Analysis process because it acts as a basis for other processes. This documentation would be referred in design, development and testing phases significantly. Documentation could include both internal as well as external documentation. III. Plan A plan is essential at every stage of software life cycle process but becomes very vital for requirements analysis phase. Plan consists of object ives, scope, assumptions, constraints, risks, milestones, deliverables, methods, resources and schedules involved in requirements analysis. There may be a large overlap between contract and plan. Whereas a contract is generally between two parties, a plan may not be shared with the other party. IV. Policy Policy is a set of rules or