1 Concept of Operations and Business Modelling(c) J.Nawrocki Lecture 3 Requirements Engineering & Project Management Lecture 2 Concept of Operations and Business Modelling Req. Eng. & Project Manag.
2 Introduction Chaos + computers = Computerized chaosJ.Nawrocki, Business Modelling
3 (c) J.Nawrocki Bibliography Lecture 3 ISO/IEC Standard for Information Technology—Software life cycle processes—Life cycle data, IEEE/EIA , April 1998. IEEE Guide for Information Technology – System Definition - Concept of Operations (ConOps) Document, IEEE Std , March 1998. J.Nawrocki, Business Modelling Req. Eng. & Project Manag.
4 Rational Unified ProcessProject statement Rational Unified Process What is the problem? Who suffers? What are the implications? How to solve it? J.Nawrocki, Business Modelling
5 They can only give answers. They can’t ask questions.Project statement What is the problem? Who suffers? What are the implications? How to solve it? Computers are useless. They can only give answers. They can’t ask questions. Pablo Picasso J.Nawrocki, Business Modelling
6 Project statement What is the problem? Who suffers? What are the implications? How to solve it? Long queues of applicants for studying at the Faculty of Computing and Management J.Nawrocki, Business Modelling
7 Workers of the Dean OfficeProject statement What is the problem? Who suffers? What are the implications? How to solve it? The applicants Workers of the Dean Office J.Nawrocki, Business Modelling
8 The applicants are loosing their timeProject statement What is the problem? Who suffers? What are the implications? How to solve it? The applicants can change their minds and they can go to other university The applicants are loosing their time The Dean Office workers are unsatisfied J.Nawrocki, Business Modelling
9 Advantage: Simple Disadvantage: More workers requiredProject statement What is the problem? Who suffers? What are the implications? How to solve it? Parallel teams Inf AiZ Advantage: Simple Disadvantage: More workers required J.Nawrocki, Business Modelling
10 Advantage: Less work Disadvantage: CostProject statement What is the problem? Who suffers? What are the implications? How to solve it? Internet Enrollment System Dean office Applicants Internet Advantage: Less work Disadvantage: Cost J.Nawrocki, Business Modelling
11 Agenda IEEE/EIA Standard 12207-1997 IEEE Standard 1362-1998Business Modelling Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions J.Nawrocki, Business Modelling
12 6.2 Change request or modification request ISO/IEC contents 6.1 Acquisition plan 6.2 Change request or modification request 6.3 Concept of operations description 6.4 Database design description 6.5 Development process plan 6.6 Evaluation records 6.8 Maintenance process plan 6.9 Operation process plan 6.10 Problem report and problem resolution report 6.11 Project management plan 6.12 Software architecture description . . . J.Nawrocki, Business Modelling
13 Concept of Operations - 12207Purpose: Describe, in users’ terminology, how the system should operate to meet the users’ needs. Content: a) Generic description information; Date of issue: Status: Draft Issuing organization: SDS Cover page Change history Summary References Glossary J.Nawrocki, Business Modelling
14 Concept of Operations - 12207Purpose: Describe, in users’ terminology, how the system should operate to meet the users’ needs. Content: a) Generic description information; b) Description of current situation or system; c) Justification for and nature of changes; d) Concepts for the proposed system; J.Nawrocki, Business Modelling
15 Current situation Proposed system ChangeBusiness Modelling Current situation Proposed system Change J.Nawrocki, Business Modelling
16 Concept of Operations - 12207Purpose: Describe, in users’ terminology, how the system should operate to meet the users’ needs. Content: a) Generic description information (previous slide); b) Description of current situation or system; c) Justification for and nature of changes; d) Concepts for the proposed system; Use cases e) Operational scenarios; f) Summary of impacts; g) Analysis of the proposed system; h) Priorities, assumptions, constraints, advantages, limitations, alternatives, and trade-offs considered. J.Nawrocki, Business Modelling
17 Podanie Propozycje poprawy 1 Kandydat wprowadza podanie przez InternetKsantypa 2 Podanie J.Nawrocki, Business Modelling
18 2 Kandydat opłaca rekrutacjęPropozycje poprawy 2 Kandydat opłaca rekrutację Wystarczy? J.Nawrocki, Business Modelling
19 3 Ksantypa ściąga z KReM-u wyniki matury kandydataPropozycje poprawy 3 Ksantypa ściąga z KReM-u wyniki matury kandydata Ksantypa 2 KReM J.Nawrocki, Business Modelling
20 4 Kandydat sprawdza swoje wynikiPropozycje poprawy 4 Kandydat sprawdza swoje wyniki Ksantypa 2 KReM Fizyka % J.Nawrocki, Business Modelling
21 5 Ksantypa podaje wyniki rekrutacjiPropozycje poprawy 5 Ksantypa podaje wyniki rekrutacji Jan Abacki 1999 Ewa Backa 1998 ... Ksantypa 2 J.Nawrocki, Business Modelling
22 6 Wydziałowa Komisja Rekrutacyjna odbiera dokumentyPropozycje poprawy 6 Wydziałowa Komisja Rekrutacyjna odbiera dokumenty J.Nawrocki, Business Modelling
23 Agenda IEEE/EIA Standard 12207-1997 IEEE Standard 1362-1998Business Modelling Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions J.Nawrocki, Business Modelling
24 1998: IEEE Std 1362-1998 by R. Thayer, R. Fairley, P. Bjorke.IEEE Std 1362 History 1980: R.J. Lano, A Structured Approach for Operational Concept Formulation, TRW SS-80-02, Redondo Beach, CA. 1992: Software Systems Technical Committee of the American Institute of Aeronautics and Astronautics (AIAA), A standard for an Operational Concept Document. 1993: MS thesis, California State University, Sacramento; accepted as MIL-STD-498. 1998: IEEE Std by R. Thayer, R. Fairley, P. Bjorke. J.Nawrocki, Business Modelling
25 3. Current system or situation ConOps structure 1. Scope 2. Referenced documents 3. Current system or situation 4. Justification for and nature of changes 5. Concepts for the proposed system 6. Operational scenarios 7. Summary of impacts 8. Analysis of the proposed system 9. Notes Appendices Glossary J.Nawrocki, Business Modelling
26 Operational scenariosA step-by-step description of system’s operation and interaction with its users and external interfaces under a given set of circumstances. J.Nawrocki, Business Modelling
27 The same structure ConOps structure - 1362 1. Scope2. Referenced documents 3. Current system or situation 4. Justification for and nature of changes 5. Concepts for the proposed system 6. Operational scenarios 7. Summary of impacts 8. Analysis of the proposed system 9. Notes Appendices Glossary The same structure J.Nawrocki, Business Modelling
28 Current / proposed system description3.1 Background, objectives, and scope 3.2 Operational policies and constraints Constraints on the hardware, the hours of operation of the system, the number of available personnel, .. J.Nawrocki, Business Modelling
29 Current / proposed system description3.1 Background, objectives, and scope 3.2 Operational policies and constraints 3.3 Description of the current system or situation The operational environment Major system components and their interconnections Interfaces to external systems or procedures Functions (features) Inputs, outputs, data flows Cost of system operations Operational risk factors Performance // Safety and security aspects // ... J.Nawrocki, Business Modelling
30 Current / proposed system description3.1 Background, objectives, and scope 3.2 Operational policies and constraints 3.3 Description of the current system or situation 3.4 Modes of operation for the current system or situation Operational, degraded, maintenance, training, .. 3.5 User classes and other involved personnel 3.5.1 Organizational structure 3.5.2 Profiles of user classes 3.5.3 Interactions among user classes 3.5.4 Other involved personnel 3.6 Support environment J.Nawrocki, Business Modelling
31 Current / proposed system description3.1 Background, objectives, and scope 3.2 Operational policies and constraints 3.3 Description of the current system or situation 3.4 Modes of operation for the current system or situation 3.5 User classes and other involved personnel 3.5.1 Organizational structure 3.5.2 Profiles of user classes 3.5.3 Interactions among user classes 3.5.4 Other involved personnel 3.6 Support environment J.Nawrocki, Business Modelling
32 Agenda IEEE/EIA Standard 12207-1997 IEEE Standard 1362-1998Business Modelling Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions J.Nawrocki, Business Modelling
33 3. Current system or situation ConOps structure 1. Scope 2. Referenced documents 3. Current system or situation 4. Justification for and nature of changes 5. Concepts for the proposed system 6. Operational scenarios 7. Summary of impacts 8. Analysis of the proposed system 9. Notes Appendices Glossary J.Nawrocki, Business Modelling
34 Business-level use-cases (processes) Information objects (data)Business modelling Actors Business-level use-cases (processes) Information objects (data) J.Nawrocki, Business Modelling
35 Overview of RE guidelinesBasic Interm Adv 8 6 5 4 3 2 36 - 6 2 1 3 21 - 1 2 4 9 The requirements document Requirements elicitation Reqs analysis & negotiation Describing requirements System modelling Requirements validation Requirements management RE for critical systems J.Nawrocki, Business Modelling
36 Develop complementary system modelsBasic guidelines System modelling Develop complementary system models J.Nawrocki, Business Modelling
37 NoweNazwisko(string)Class Diagrams Człowiek Imię: string Nazwisko: string RokUrodz: int NoweNazwisko(string) Mąż Żona 1 1 DataŚlubu: string DataŚlubu: string {Mąż.DataŚlubu == Mąż.Żona.DataŚlubu} J.Nawrocki, Business Modelling
38 Kawaler Żonaty Rozwodnik WdowiecState diagrams Kawaler / Narodziny Żonaty Znalazł wybrankę [wiek > 18] / Ślub Znalazł wybrankę / Ślub Znalazł wybrankę / Ślub / Rozwód Rozwodnik Wdowiec Śmierć żony / Owdowienie J.Nawrocki, Business Modelling
39 wprowadzenie REGON-u IOSequence diagrams Rejestrator System wprowadzenie REGON-u IO REGON jest poprawny pozostałe dane IO dane są poprawne dane jednostek IO J.Nawrocki, Business Modelling
40 Develop complementary system models Model the system’s environmentBasic guidelines System modelling Develop complementary system models Model the system’s environment J.Nawrocki, Business Modelling
41 Business Process DiagramWprowadzenie Business Process Diagram BPMN 1.0, May 2004 BPEL4WS – wykonanie procesów J.Nawrocki, Business Modelling
42 Wprowadzenie Obiekty przepływu Obiekty łączące Tory pływackieArtefakty J.Nawrocki, Business Modelling
43 Obiekty przepływu Zdarzenia Czynności Bramki Adnotacje Tekst adnotacjiJ.Nawrocki, Business Modelling
44 Prosty diagram procesów (S. White)J.Nawrocki, Business Modelling
45 Obiekty łączące Przepływ sterowania Przepływ wiadomości PowiązaniaJ.Nawrocki, Business Modelling
46 Diagram procesów z zależnościami czasowymi (S.White)J.Nawrocki, Business Modelling
47 Tory pływackie Nazwa Basen Nazwa Tory Nazwa NazwaJ.Nawrocki, Business Modelling
48 Diagram procesów z basenami (S.White)J.Nawrocki, Business Modelling
49 Artefakty Obiekty danych Grupy J.Nawrocki, Business Modelling
50 Diagram procesów dla PRINCE2J.Nawrocki, Business Modelling
51 At last! Summary ConOps standards: 12207 + 1362Business modelling: actors, processes, information objects Current system, nature of change, the proposed system J.Nawrocki, Business Modelling
52 ? Questions? J.Nawrocki, Business Modelling (c) J.Nawrocki Lecture 3Req. Eng. & Project Manag.
53 1. What is your general impression? (1 - 6) Quality assessment 1. What is your general impression? (1 - 6) 2. Was it too slow or too fast? 3. What important did you learn during the lecture? 4. What to improve and how? J.Nawrocki, Business Modelling