Premium
8.6.4 A CDROM Systems Engineering Book of Knowledge (CD‐SEBOK)
Author(s) -
Beshore David G.,
Patmor Lynette L.,
Wilson Willie B.
Publication year - 2001
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2001.tb02404.x
Subject(s) - computer science , hypertext , world wide web , server , hyperlink , process (computing) , software engineering , the internet , engineering , web page , operating system
Since 1997, our systems engineering (SE) process organization developed tools, techniques, and methods using commercial‐off‐the‐shelf (COTS) tools and Internet Servers to collect and deploy systems engineering knowledge. The phases of development described, herein, explain the rapid growth and contributions that began with a single dedicated web‐based PC server and culminated in a CDROM‐based Systems Engineering Book of Knowledge (CD‐SEBOK) from a network of servers. The development steps included: Initially providing content on a single SE process –‘requirements’ on prototype server (1997), then Expansion to six (6) processes for the entire SE department (1998), then Validation of content by process owners (1998), then Transfer of content to CDROM to provide a virtual web, version control and personal search engine, (1999)and finally, Expansion of content from multiple business site websites (1999) and then Recapture on CDROM (2000). Content is currently 640 Mbytes of highly linked (8300 hyperlinks) information related to systems engineers and is considered to be a book of knowledge for systems engineers throughout the company. The content also is used in internal and external assessments for the Capability Improvement Models, such as SW‐CMM, CMMI and SECM (EIA‐731). The development process included many object‐oriented (OO) methods that provided a complete and efficient method to gather requirements for the server and the development of a CDROM with a powerful search engine. These methods include uses cases, content classes, collaboration, sequence, state and deployment diagrams. A new lifecycle method, called Synchro‐X tm (Beshore 1999), was used during the specification, design, build and verification phases to reduce risk during development along with object oriented techniques (Ericksson 1999). The model forces different reviews among distinct teams to provide necessary inputs during product development. The development of the CD‐SEBOK contained inherent risks: Lack of Resources or Commitment Requirements Misunderstanding Misunderstanding of Web Content Scope Inadequate Password Protection Information Security Misunderstanding SE Common Processes Not Identified at Business Site Level The integration team (20 people from various business sites) was responsible for identifying and managing risk that might preclude successful completion of the team's responsibilities and implementation of the CD‐SEBOK. It was the responsibility of each team member to constantly evaluate and identify any issue/problem that could adversely impact the CD‐SEBOK.