111213 the model is known as furps functionality

  • Stanford University
  • MS&E 264
  • Notes
  • CorporalStarGoat9916
  • 54
  • 100% (1) 1 out of 1 people found this document helpful

This preview shows page 39 - 41 out of 54 pages.

11,12,13The model is known as FURPS:Functionality (feature set, capabilities, generality, security)Usability (human factors, aesthetics, consistency, documentation)The Product Development Process197BaselineReleaseBranchR.2i.1R.2i.2R.1IntegrationBranchIntegrationBranchIntegrationBranchR.1i.1SWCSWC Assigned toDevelopersR.0R.2R.3R.40SWCSWC001012SWCSWC01SWC112000111120Figure 5.14.Product Life Cycle—Software Configuration Management and Release. SWC, Software Changes.
Reliability (frequency and severity of failures, recoverability, predictability, accu-racy, MTBF or mean time between failures)Performance (speed, efficiency, resource consumption, throughput, response time)Supportability (ability to be tested, extended, adapted, maintained, compatible,configurable, serviced, installed, localized for non-English users)Grady (1992, 1997)11,12and Grady and Caswell (1998)13may be consulted for a detailed dis-cussion of this model and the indicators in the software development process.5.13.4 Effectiveness of the Software Development ProcessThe Carnegie Mellon University Software Engineering Institute (SEI) has developed an excel-lent model that is recommended for assessing the quality of a software development process inan organization.14The SEI model defines five levels of maturity in the process capability of asoftware organization:Initial—Few processes are defined and success depends on the heroic efforts ofindividuals.Repeatable—Disciplined project management processes are in place.Defined—A consistent set of standard engineering and management processes arein place.Managed—A predictable process is in place and the process and product qualitymetrics are measured and tracked.Optimized—The process is continuously improved.A software manager can use this model to assess the maturity level for software develop-ment in his/her organization and can identify corrective actions that are required to move upthe maturity scale.15Critical elements in developing a reliable software product and the recommended guide-lines include:161.Adherence to a Software Development Process:Identify the factors that impact software reliability and determine how to meas-ure them. These factors and how they are measured depend on the applicationtype (real-time software or not), the company’s software organizational struc-ture (does it include independent departments for testing, quality assurance,and configuration management?), the size and complexity of the softwareproduct (number of modules and lines of code per module), the software lan-guage, the development tools, and the project schedule.Track the project and the software quality metrics, including the number andtypes of defects, the size and complexity of the software product, and theresources expended over the project schedule.

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 54 pages?

Upload your study docs or become a

Course Hero member to access this document

Term
Fall
Professor
Rafinejad
Tags
Marketing, product development process, Product Development and Commercialization

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture