Hardware Reference
In-Depth Information
The structure of these two semantic wikis is given in figure 3.
Fig. 3.
A model of 12207 and 24765 semantic wikis
5.3 The Project in Action
The two latter authors both worked for nearly ten years at Thales Information System
(formerly Syseca Inc), a software services company. They led projects and developed
several management information systems under the control of Thales Information
System corporate baseline.
The authors have defined an apprenticeship/production framework called ILI (
In-
génierie du Logiciel par Immersion
, Software Engineering by Immersion), based on a
reference model, a development cycle and a typical WBS (Working Breakdown
Structure: a deliverable-oriented hierarchical decomposition of the work to be exe-
cuted by the project team to accomplish the project objectives and create the required
deliverables. It organizes and defines the total scope of the project [18]).
The Process Reference Model (PRM) is adapted and simplified from ISO/IEC
12207; we are using 3
process groups
organizing 13 processes:
Software Develop-
ment Engineering
(Requirements capture, Software Requirements Analysis, Software
Architectural Design, Software Detailed Design, Software Construction, Software
integration; Software qualification testing);
Software Project Management
(Project
Management, Quality Assurance, Configuration Management); and
Software Devel-
opment Support
(Infrastructure Management, Life Cycle Model Management, Docu-
mentation Management, Installation-Operation).
We use a Y-shaped life cycle that separates resolution of technical issues from
resolution of feature issues [19]. First, the cycle is divided into two branches (tracks):
a functional track and a technical track. Then these two tracks amalgamate for the
realization of the system.
The WBS has a structural and a temporal decomposition. Each process is structur-
ally decomposed in Software Engineering activities (to distinguish it from the activi-
ties in the 12207 sense) that may have slightly variation from a project to another.
Each Software Engineering activity is further decomposed in sub-activities that can be
fully specified or just named, depending of the scope and goals of the project. The
WBS is temporally organized in stages (in our case, 9 of 2 week each). The planning
