1. Abstract & Introduction………………………………………………………... 3IntroductionThis document offers guidance for the optimal development of platform-based design of a commercial product by defining a repeatable process of development. We have focused on the identification, traceability and V&V of architectural driver requirements, which are common to all the product variants.2. Overview of Process to Design a Family of ProductsPrimary System Actors – These system actors represent the platform design of the Answering Machine System.System BoundaryUse Case 1: Turn Answering Machine On or OffActivity Diagram:Use Case 2: Set Data Use Case 3: Pick-up phone callUse Case 4: Receive Incoming MessageUse Case 5: Retrieve InformationUse Case 2.2: Set Settings USE CASE 4Use Case 4.1: Record Incoming Message Use Case 4.2: Insert Data StampUse Case 4.3: Display Incoming Message Received USE CASE 5Use Case 5.1: Play Outgoing MessageUse Case 5.2: Playback Incoming MessagesUse Case 5.4: Delete Incoming MessageHigh Level (Level 1) Requirements from Use CasesRequirements TraceabilitySystem Logical Design6. Family of Answering Machine by FeaturesHIGH-END MODELTTY TEXT MODELBRAILLE MODEL9. ConclusionPlatform Based Design Process of a Standard Commercial Product:Answering Machine SystemSubmitted By: Project For:Elizabeth Koza Dr. AustinRocio Salas-Lopez ENPM 643Vanessa Virtudazo Fall 2004Table of Contents1. Abstract & Introduction………………………………………………………... 32. Overview of Process to Design a Family of Products…………………………..43. Goals, Scenarios, & Use Cases………………………………………………… 74. Generation of Requirements……………………………………………………275. Abstraction of System Models………………………………………………….316. Product Features of the Product Variants………………………………………347. Architectural Drivers…………………………………………………………...398. System Validation & Verification Plan………………………………………...439. Conclusion……………………………………………………………………...5410. Future Work & Technology Advances…………………………………………5511. References………………………………………………………………………5821. AbstractThe demand for new commercial products is increasing at an accelerated pace. The communication revolution has allow for the development of a global market economy in which competing industries strive to satisfy the diverse needs of billions of individuals in order to survive. But with the daily innovations and technology advances, each with different infrastructure requirements, configuration management and interoperability of products and systems is far from ideal. Add to this the constant pressures and demands from corporate management to shorten product development times, while reducing total production cost and we move closer into the chaotic arena. With the years, these new-age challenges have produced the appropriate stage for Systems Engineering methodologies to be recognized and adopted by all private and public institutions. Although the inception of System Engineering can be traced back to the Cold War era when the Department of Defense imposed the first quality standard on special programs like the Polaris (later Poseidon and currently Trident), the full suite of SE methodologies has been misunderstood and underappreciated by the private industry sector for decades. However, current challenges confronting manufacturing enterprises have forced the larger corporations to adopt pieces of SE methodologies under different names (i.e. Six Sigma, Life Cycle Management, Total Quality Management, and among others). In this paper we have chosen to propose a framework based on SE methodologies learnedin ENPM 641, 642 and 643 that allows the design of a family of answering machines. We have chosen to expand the SE paper that we generated during the ENPM642 class of Spring 2002 and introduce new SE elements that allow for better identification of platform requirements, improve traceability, validation and verification. IntroductionThis document offers guidance for the optimal development of platform-based design of a commercial product by defining a repeatable process of development. We have focusedon the identification, traceability and V&V of architectural driver requirements, which are common to all the product variants. One of the industry drivers of this movement is the need to facilitate development of future product generations that are extensions of original hardware and software investments, thus allowing for reduced time to market, while decreasing development andproduction costs. Another driver is the need to control the ever-increasing cost attached to the verification and testing of each new component introduced in an already complex system. Component communality leads to process communality advantages in areas like testing, validation and verification.There can be re-use at the different levels of abstraction. However, the benefits of re-use will be the most beneficial at lower levels of abstractions. In the case of our project, we 3have focused much effort in re-using components in the distinct products, so that we can obtain and verify the benefits of the “re-use” concept.2. Overview of Process to Design a Family of ProductsThe following process defines a development path for generating a family of products:1) Select the Design Team: All systems and products are the effort of a group of individuals with different specialties (i.e. structural engineers, software developers, electrical engineers, marketers, etc). The start of the product development phase begins with the selection of the design team.2) Goals and Scenarios: The design team determines the goal of the family of products by analyzing and interpreting market data. In this case our goal is to design a family of answering machines. The goal can start with a generalization, but the subsequent definition of Use-Cases Scenarios help gather more specific information about the customer needs.3) High Level Requirements: These requirements are derived from the Use-Case Scenarios and specify the “what” of the system without compromising the architectural design.4) Define