![]() |
![]() |
![]() |
|
| Annex 2 | |||
| 2.7 The Complex Method SEtec |
SEtec - Software Engineering Technolog
Contents
|
|
|---|
1 Brief Description
SEtec Lifecycle Process and Result Model:
The SEtec lifecycle process model is comprised of five phases. SEtec specifies the results to be achieved as well as the corresponding evaluation methods to be applied.
Result: Preliminary concept with description of the business-oriented tasks, the organizational structure, and the preliminary data model
Result: User-level concept with function model, entity relationship model, user interface with dialog sequences and mask layouts
Result: DP concept, consisting of system model, logical data model as logical relational model
Result: Software system, physical database, integrated and tested software system
Result: Application system ready to be used
Methodical components of SEtec are:
Organizational Charts represent the tree-like structure of organizational units The definition of organizational units complete the description of organizational structures.
Modeling business-oriented structures is supported by task hierarchy diagrams and task sequence diagrams. Task sequence diagrams illustrate the cooperation of tasks, information flows, sources and sinks.
The data modeling in SEtec is based on the Entity Relationship approach.
Modeling the logical relational model comprises the techniques of the normalization, graphic relational models, and merging and segmentation of tables.
This method is illustrated by means of a set of mapping rules and by a tool based on these rules.
Function modeling is supported by the techniques functional hierarchy diagram and functional sequence diagram. Functional sequence diagrams describe the dynamic interaction of functions, messages, and user actions. SEtec knows the following functional sequence diagrams. Sequence Overview, Dialog Sequence, Batch Sequence, and Menu Sequence.
Pseudocode as Structured English and COBOL as Program Design Language.
Project Control and Management supports the project organization by means of task and deliverable models mapped as object class structures, techniques of the project and resource planning, transitions between tasks controlled by state automata, and accounting of schedules and efforts.
All the results of all phases are subject to a static analysis. Typical are static tests with regard to completeness and with regard to the consistency between results. Reports refer to violations. - Test Methods Method Test has been defined for results of phases Implementation, Integration, and Test.
Hierarchically structured objects having no "individual" diagram technique can generally be graphically represented as "Structure Plan" and be manipulated by the operations Delete, Display Characteristics, Browse.
The SEtec methods are integrated via the phases. The integration is illustrated by the general automatic mapping of results from one phase to the result structure of the following phase, i. e. in the sense of a First Cut. The product SEtec was designed by Softlab GmbH. SEtec has been applied in a great number of companies and is constantly upgraded. The present representation refers to version SEtec 2.0 of February 1993.
2 Tabular Comparison
|
Comparison of the Basic Methods and the Methodological Components of SEtec |
|
|---|---|
| AUD - Audit | |
| ACC - Analysis of Covert Channels | |
| BAR - Bar Plan | |
| TREE - Tree Diagram |
Result Structures as Tree Diagram Report /PCMS, 1992/, chap. 9: Reports (Graphic Reports) (*) |
| BBTD - Black Box Test Case Design |
Black Box Test Case Design in Phase 4 /TEC-Meth, 1993/, chap. 5, sections 2.2.3 to 2.2.5 |
| CRC - Class Responsibility Collaboration | |
| DIAL - Dialog Design Modeling |
Phase 2: Functional Sequence Diagram /TEC-Meth, 1993/, chap. 3, section 6.3.2 "Menu Sequences" (*) |
| DFM - Data Flow Modeling |
Phase 1: Task Sequence Diagram /TEC-Meth, 1993/, chapter 2, section 3.2 "Flow Chart" Phase 2: Functional Sequence Diagram /TEC-Meth, 1993/, chap. 3, section 6.3 "Dynamic Function Model" (*) |
| DNAV - Data Navigation Modeling | |
| DVER - Design Verification | |
| ELH - Entity Life History | |
| ER - E/R Modeling |
Phases 1 and 2: ER Modeling and ERM Diagrams /TEC-Meth, 1993/, chapter 3, section 5 "Data Model" (*) |
| DTAB - Decision Table Technique | |
| EVT - Earned Value Method | |
| EXPM - Expertise Model | |
| FCTD - Functional Decomposition |
Phase 1: Task Hierarchy Diagram /TEC-Meth, 1993/, chap. 2, section 3.3 "Task Hierarchy" Phase 2: Functional Hierarchy Diagrams /TEC-Meth, 1993/, chapter 3, section 6.2 "Static Function Model" (*) |
| FMEA - Failure Mode Effect Analysis | |
| FNET - Function Net Modeling | |
| FS - Formal Specification | |
| IAM - Interaction Modeling | |
| CFM - Control Flow Modeling |
Phase 2: Functional Sequence Diagram /TEC-Meth, 1993/, chapter 3, section 6.3 "Dynamic Function Model" |
| COM - Class/Object Modeling | |
| LOGM - Logical DB Modeling |
Transition from Phase 2 to Phase 3: Method and automated Mapping ERM ! Logical Relational Model /TEC-Meth, 1993/, chapter 4, section 5.2 "Relational Data Model" (*) |
| MODIAG - Module Diagrams | |
| NORM - Normalization |
Phase 3: Normalization up to 3. NF /TEC-Meth, 1993/, chapter 4, section 5.2.2 "Developing the Data Model" (*) |
| NPT - Network Planning Technique |
PCMS Technique as Network Planning Technique over all Phases: PCMS = Project Control and Management System /PCMS, 1992/, chap. 3 "Tasks and Results" (*) |
| BA - Benefit Analysis | |
| ODT - Object Design Technique | |
| OGC - Organizational Chart |
Phase 1: Organizational Diagram /TEC-Meth, 1993/, chap. 2, section 5.1 "Organizational Diagram" (*) |
| PCODE - Pseudocode |
Phase 3 and 4: Action Diagrams /CTWS-PDT, 1993/, chap. 3 "The Action Diagram Editor" (*) |
| PRODIAG - Process Diagrams | |
| PVER - Program Verification | |
| PIM - Process Interaction Modeling | |
| REV - Review |
Phase 4: Test Review /TEC-Meth, 1993/, chapter 5, section 6 "Test" (*) |
| SIMU - Simulation Models | |
| EMOD - Estimation Models | |
| SSM - Subsystem Modeling | |
| STAT - Static Analysis |
over all phases supported by methods and automated with consistency reports (*) |
| STRD - Structured Design |
Phase 3: Method "Modularization" representable as tree diagram report (compare Tree) /TEC-Meth, 1993/, chap. 4, section 6 "System Model" (*) |
| SBM - System Behavior Models | |
| T - Test |
Phase 4: Implementing the Method Test /TEC-Meth, 1993/, chap. 5 "Test" (*) |
| TRDA - Trend Analysis | |
| UCM - Use Case Modeling | |
| WBTD - White Box Test Case Design |
Phase 4: Implementing the Method Test /TEC-Meth, 1993/, chap. 5 "Test" (*) |
| STM - State Transition Modeling | |
| STMO - State Modeling in the OO Field | |
| RELM - Reliability Models | |
3 Specification of the Allocation
| Method | Corresponding Component in SEtec | Explanation |
|---|---|---|
| BBTD Black Box Test Case Design | Black Box Test Case Design in Phase 4 /TEC-Meth, 1993/, chap. 5, sections 2.2.3 to 2.2.5 |
SEtec covers the following parts of this basic method with equivalent methods:
|
| CFM Control Flow Modeling | Phase 2: Functional Sequence Diagram /TEC-Meth, 1993/, chap. 3, section 6.2 "Dynamic Function Model" | The functional sequence diagrams partly comprise the modeling of control flows. They are not identical, however, with the control flow diagrams illustrated in CFM. The functional sequence diagrams combine functions and user actions by means of messages. Messages transmit control flows and data in form of attributes and signals. Signals are e. g. the return of state information in the result of a function or user action. |
4 Literature
![]() |
![]() |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |