Concept of Operations and Business Modelling

1
Concept of Operations and Business Modelling
Requirements Engineering Project
Management Lecture 2

• Jerzy.Nawrocki_at_put.poznan.pl
• www.cs.put.poznan.pl/jnawrocki/require/

2
Introduction
Chaos
Computerized chaos
computers
3
Bibliography

• ISO/IEC 12207 Standard for Information
  TechnologySoftware life cycle processesLife
  cycle data, IEEE/EIA 12207.1-1997, April 1998.
• IEEE Guide for Information Technology System
  Definition - Concept of Operations (ConOps)
  Document, IEEE Std 1362-1998, March 1998.

?
4
Project statement
Rational Unified Process

• What is the problem?
• Who suffers?
• What are the implications?
• How to solve it?

5
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 cant ask questions.
6
Project statement
What is the problem? Who suffers? What are the
implications? How to solve it?
7
Project statement
What is the problem? Who suffers? What are the
implications? How to solve it?

• The applicants
• Workers of the Dean Office

8
Project 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

9
Project statement
What is the problem? Who suffers? What are the
implications? How to solve it?
Advantage Simple Disadvantage More
workers required
10
Project statement
What is the problem? Who suffers? What are the
implications? How to solve it?
Internet Enrollment System
Advantage Less work
Disadvantage Cost
11
Agenda

• IEEE/EIA Standard 12207-1997
• IEEE Standard 1362-1998
• Business Modelling

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

12
ISO/IEC 12207 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 . . .
13
Concept of Operations - 12207
Purpose Describe, in users terminology, how the
system should operate to meet the users
needs. Content a) Generic description
information
Change history Summary References Glossary
14
Concept of Operations - 12207
Purpose 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
15
Business Modelling
Current situation
Proposed system
Change
16
Concept of Operations - 12207
Purpose 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
e) Operational scenarios
f) Summary of impacts g) Analysis of the
proposed system h) Priorities, assumptions,
constraints, advantages, limitations,
alternatives, and trade-offs considered.
17
Propozycje poprawy
1 Kandydat wprowadza podanie przez Internet
Ksantypa 2
Podanie
18
Propozycje poprawy
2 Kandydat oplaca rekrutacje
Wystarczy?
19
Propozycje poprawy
3 Ksantypa sciaga z KReM-u wyniki matury kandydata
Ksantypa 2
KReM
20
Propozycje poprawy
4 Kandydat sprawdza swoje wyniki
Ksantypa 2
KReM
Fizyka ..... 1
21
Propozycje poprawy
5 Ksantypa podaje wyniki rekrutacji
Jan Abacki 1999 Ewa Backa 1998 ...
Ksantypa 2
22
Propozycje poprawy
6 Wydzialowa Komisja Rekrutacyjna odbiera
dokumenty
23
Agenda

• IEEE/EIA Standard 12207-1997
• IEEE Standard 1362-1998
• Business Modelling

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

24
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 1362-1998
by R. Thayer, R. Fairley, P. Bjorke.
25
ConOps structure - 1362
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
26
Operational scenarios
A step-by-step description of systems operation
and interaction with its users and external
interfaces under a given set of circumstances.
27
ConOps structure - 1362
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
28
Current / proposed system description
3.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, ..
29
Current / proposed system description
3.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 // ...
30
Current / proposed system description
3.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
31
Current / proposed system description
3.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
32
Agenda

• IEEE/EIA Standard 12207-1997
• IEEE Standard 1362-1998
• Business Modelling

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

33
ConOps structure - 1362
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
34
Business modelling

• Actors
• Business-level use-cases (processes)
• Information objects (data)

35
Overview of RE guidelines
The requirements document
Requirements elicitation
Reqs analysis negotiation
Describing requirements
System modelling
Requirements validation
Requirements management
RE for critical systems
36
Basic guidelines

• Develop complementary system models

37
Class Diagrams
Czlowiek
Imie string Nazwisko string RokUrodz int
NoweNazwisko(string)
Zona
Maz
1
1
DataSlubu string
DataSlubu string


Maz.DataSlubu Maz.Zona.DataSlubu
38
State diagrams
39
Sequence diagrams
Rejestrator
System
40
Basic guidelines

• Develop complementary system models
• Model the systems environment

41
Wprowadzenie
Business Process Diagram
BPMN 1.0, May 2004
BPEL4WS wykonanie procesów
42
Wprowadzenie
Obiekty przeplywu Obiekty laczace Tory
plywackie Artefakty
43
Obiekty przeplywu
Zdarzenia
44
Prosty diagram procesów (S. White)
45
Obiekty laczace
Przeplyw sterowania
Przeplyw wiadomosci
Powiazania
46
Diagram procesów z zaleznosciami czasowymi
(S.White)
47
Tory plywackie
Nazwa
Basen
Nazwa
Nazwa
Tory
Nazwa
48
Diagram procesów z basenami (S.White)
49
Artefakty
Obiekty danych
Grupy
50
Diagram procesów dla PRINCE2
51
Summary
At last!

• ConOps standards 12207 1362
• Business modelling actors, processes,
  information objects
• Current system, nature of change, the proposed
  system

52
Questions?
?
53
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?