System Engineering from marketing requirements to product specifications

System Engineering: from marketing requirements to product specifications Larisa Melikhova Dmitry Vavilov St. Petersburg Software Center Motorola St. Petersburg Software Center October 2008 System Engineering: from marketing requirements to UI specifications

Work process as it was Product development Testing Marketing Requirements (MR) Technical Requirements (TR) Project Functional Specifications (PFS) System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 Test suites Test cases 2

Current work process Product development Testing Marketing Requirements (MR) User Interface Technical Requirements (TR) Project Functional Specifications (PFS) System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 Test suites Test cases 3

Three views to be taken into account The view of the stakeholders whose job it is to specify the requirements (may include customers, consumers, management, etc. ) The view of the development team whose responsibility it is to provide the product that is described by the requirements. The view of the tester who must verify consistency between the stated intention of the stakeholders and the interpretation of the developer in the form of a product. Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007

3 Level Model MR/FR: Marketing level Describing functions of the device TR: System level 2 types: F (functional) and UI; mapped to FRs Mature or stable requirements that are unlikely to be changed in the foreseeable future. Invariability and possibility of being tested in a black box model PFS: Implementation level Mapped to UI TRs Requirements that are likely to vary from model to model. Include details that may relate to the product performance, power consumption, timing parameters, and so on. System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 5

System engineer’s role Gather knowledge PMR Develop & Maintain Requirements Conduct Technical Reviews Analyze Design Analyze System Architecture PFS Develop & Maintain Interfaces • Specialization: gathering knowledge • Adjustment of experts from all sides: Marketing <-> User Interface <-> Development • Considering the system as a whole • Focus on User System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 6

Requirements Guidelines Clear precise statement Unambigous Laconic Complete One response to one or more stimuli System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 Action expressed 7

Achieving Reuse Goals “Bricks” approach to reusability Each requirement is considered as a "brick" – an atomic element without product or modelspecific terms, not connected with other elements. • Removing specific details • Requirements atomicity • No references to other requirements Clear and consistent structure – – – Related requirements grouped together. Each group preceded by a precise and laconic heading. Specifications, assumptions & constraints associated with each group. Unique terminology within the grouping. Duplications and contradictions removed. System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 8

Examples of requirements ratio System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 9

SE Example: Focus Window In case of development of EPG for STB with two tuners we show some program all the time (in full screen mode or in scaled video area) The list of questions for System Engineer to describe the behaviour of STB : 1) During initialization 2) In case of conflicts for resources 3) After recorded show is finished System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 10

SE Example: Recording 2 types of recording: 1. Time frame based (DVR) 2. Event based (Guide) Questions to be answered by System Engineer: • • • How to display in the Guide Gathering and storing metadata (genre, actors, etc) Stop/cancel the recording Include time shift buffer for recording Conflict resolution System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 11

Conclusions System Engineer is an essential participant of software development process who coordinates and integrates the efforts of other players for success of the entire project. Advantages of separating the sys eng group: • Better coordination of SW development process • View to the entire system • Economy of resources (due to requirements reuse and accumulated expertise) System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 12

References • Larisa Melikhova, Albert Elcock, Andrey A. Dovzhikov, Georgii Bulatov, Dmitry O. Vavilov, " Reengineering for System Requirements Reuse: Methodology and Use -Case", Proceedings of the 11 th Annual IEEE International Symposium on Computer Electronics (ISCE 2007), 20 -23 June 2007. • Jansma, P. A. ; Derro, M. E. If You Want Good Systems Engineers, Sometimes You Have To Grow Your Own! Aerospace Conference, 2007 IEEE. 3 -10 March 2007 • A. P. Sage. Systems Engineering of Computer Based Systems: status and future perspectives. Proceedings of the 1995 International Symposium and Workshop on Systems Engineering of Computer Based Systems. 1995 System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 13

System Engineering: from marketing requirements to UI specifications 1/15/2022 Motorola Document Classification, File Name, Rev Number Add additional legal text here if required by your local Legal Counsel. MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners. © Motorola, Inc. 2007 14