LECTURE 29. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow

LECTURE 29. Course: “Design of Systems: Structural Approach”

Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics

Moscow Inst. of Physics and Technology (University)

Email: [email protected] / [email protected]

Mark Sh. Levin Inst. for Information Transmission Problems, RAS

Nov. 26, 2004

PLAN:

1.Requirements engineering: preliminaries

2.Types of requirements

2.Additions

3.Systems under analysis

4.Models

1.Preliminaries

R & Dt

Manufacturing Testing MarketingUtilization &Maintenance Recycling

0 T

1.Preliminaries

R & Dt


0 T

OLD RUSSIAN ENGINEEIRNG EXPERIENCE: NB!!!

1.Preliminaries

R & Dt


0 T


WEST EXPERIENCE:1.Ralph R. Young, The Requirements Engineering Handbook,

Artech House, 2004 (Carnegie Mellon Univ.) 2.S. Robertson, J. Robertson, Mastering the Requirements Process.

Addison-Wesley, 1999. 3.K.E. Wiegers, Software Requirements. 2nd ed., Microsoft Press

2003.

1.Preliminaries

R & Dt


0 T





2003.

JOURNALS: “Requirement Engineering” (Springer), etc.

1.Preliminaries

R & Dt


0 T





2003.

JOURNALS: “Requirement Engineering” (Springer), etc.

CONFERENCES: IEEE Requirement Engineering Conference, etc.

1.Preliminaries: Layers (product, requirements, standards)

R & Dt


0 T

1.Standards

2.Requirements

3.System (product, product family, platform)

1.Preliminaries

R & Dt


0 T

Neighbor disciplines:

1.Systems engineering (& life cycle engineering)

2.Strategic management

3.Marketing

4.Forecasting

5.Knowledge engineering (acquisition of experience)

1.Preliminaries: Main Roles and Responsibility (system testing)

TESTER:* model checking* etc..

DESIGNER:* unit test* integration test

USER(S):* functional test

SYSTEM EXPERT(SPECIALIST) :* system performance* system safety* system life cycle* new requirements* new generations* new standards

1.Preliminaries

R & Dt


0 T

SYSTEMRequirementsspecifications

DesignerUserCustomersSystem specialist

1.Preliminaries

R & Dt


0 T

SYSTEMRequirementsspecifications

DesignerUserCustomersSystem specialist

Personnel with skills (LITERACY)

1.Preliminaries

R & Dt


0 T

SYSTEMRequirementsspecification

1.Preliminaries

R & Dt


0 T

SYSTEM

Requirementsengineering

process(special project)

NB!

Requirementsspecification

1.Preliminaries

R & Dt


0 T




SOURCES:1.Information from users, etc.2.Previous experience(e.g., design, manufacturing)3.Analogue-Systems4.Use Cases

1.Preliminaries

R & Dt


0 T




SOURCES:1.Information from users2.Previous experience(e.g., design, manufacturing)3.Analogue-Systems4.Use cases

PROBLEMS & TOOLS (TECHNIQUES):1.System analysis

2.Discovering3.Acquisition of knowledge, skills, experience

4.Structuring & Integration 5.Modeling & Representation

6.Analysis of dynamics6.Testing

7.Forecasting

2.Types of requirements (a hierarchical system of requirements)

TYPES:1.Business requirements2.User’s requirements3.High-level or system requirements4.Functional requirements (things the system must do)5.Non-functional requirements (properties the system must have)6.Design requirements / design constraints7.Manufacturing constraints8.Performance requirements9.Interface requirements (with other systems)10.Qualification requirements11.Logistics requirements12.Environmental requirements13.System, subsystem and component requirements14.Reusing requirementsETC.

3.Additions

ADDITIONS:

1.Criteria for evaluation of requirements

2.Prototyping

3.Scenarios

4.Reusing requirements

3.System under analysis (hierarchical layers; product, product family)

OBJECT & HIERARCHY

1.System and / or system part (component, unit)

2.System state, group of states, state chart

3.System function, function cluster, digraph of function clusters

3.System under analysis (hierarchical layers; product, product family)

OBJECT & HIERARCHY

1.System and / or system part (component, unit)

2.System state, group of states, state chart

3.System function, function cluster, digraph of function clusters

1.SYSTEM / PRODUCT

2.PRODUCT FAMILY

3.PLATFORM

3.System under analysis (scenarios)

SCENARIOS:

1.STRUCTURE (e.g., chain, tree) of system states, functions

2.Qualitative scenarios

3.Integration of use cases & forecasting

3.System under analysis (scenarios)

SCENARIOS:

1.STRUCTURE (e.g., chain, tree) of system states, functions

2.Qualitative scenarios

3.Integration of use cases & forecasting

MODELS:1.Entity relationship2.State transition model3.Entity relationship & state transition diagrams

4.Models

MODELS:

I.HIERARCHY OF REQUIREMENTS1.Hierarchy of information

2.Integration of information (fusion), etc.

II.SCENARIOS1.Coneptual maps

2.Graph models, etc.

III.DYNAMICAL MODELING1.Simulation2.Testing, etc.

Documents

LECTURE 29. Course: “Design of Systems: Structural Approach” Dept. “Communication Networks &Systems”, Faculty of Radioengineering & Cybernetics Moscow