Use Case 2: Other Engineers

From SEBoK
Revision as of 10:36, 26 August 2012 by Araher (talk | contribs) (Vignette: Software Engineer)
Jump to: navigation, search

Successful complex systems require bringing specialties together. This makes the SEBoK useful to engineers with backgrounds in biomedical, civil, electronics, chemical, civil, materials, mechanical, software, and many other specialties.

Studying the SEBoK enables engineers from disciplines other than systems engineering to:

  • see why good systems engineering practice must involve multiple disciplines
  • appreciate a broader view of systems beyond their specialties
  • understand how their contributions fit into the larger systems picture
  • prepare to solve more difficult and encompassing problems

In many cases, engineers who study systems engineering as a supplement to their non-SE specialities find their professional value enhanced when they put the new knowledge into practice.

Use of Topics

For engineers from non-SE backgrounds, each part of the SEBoK contributes something to the experience of learning about systems engineering:

Engineers may be tempted to skip over knowledge areas or topics which sound more like management than engineering stories, for example Part 3 or Part 5. This temptation should be resisted, because these topics are actually about how SE orchestrates the efforts of multiple disciplines, not management in the administrative sense.

Finally, the extensive lists of references throughout the SEBoK provide a basis for further readings.

Vignette: Software Engineer

Jose Wilks is an entrepreneurial software engineer who wants to learn more about systems engineering principles applied to embedded systems for advanced document identification and verification. He wants to implement best practices in developing highly secure systems for real-time image processing and forensic verification of documents. His company provides a rapid, secure and cost-effective solution for verifying the authenticity of identity, travel and financial documents, with technology that runs on proprietary tablet computers for portable and fixed locations.

Jose is knowledgeable about computer hardware engineering, low-level interfaces between hardware and software, and the related tradeoffs in embedded devices. His company has developed research prototypes, but without the stringent security requirements for actual field usage linked to government identification databases. The few experimental units which have been sold have fared well in limited testing, but Jose wants to expand into markets for government agencies, law enforcement departments and the private sector. To make headway into those diverse markets, he will need to confront abundant new constraints and challenges.

Jose begins his study of SE by skimming the SEBoK 1.0 Introduction and the Scope and Context of the SEBoK to get an overview of the SEBoK contents. As he reads, he sometimes refers to the Software Engineering Body of Knowledge (SWEBoK), which Jose already knows from his many years of experience on software projects. In the SEBoK, Jose is looking for nuggets of knowledge and pointers he thinks will help his enterprise expand. Here are his notes:

  • Part 3: SE and Management has concepts that are new to us and that may work. Extra system-level V&V gates identified in Life Cycle Models can be incorporated in company processes, and the references can help with implementation details. There is also material about system-wide procedures beyond software V&V, and about where to find testing and regulation standards used by various government entities. Together with the traditional software testing already in place, these processes could ensure conformity to the regulations and expedite the product's approval for use.
  • Though the system concept is proven, the company must still convince potential buyers of the system's financial benefits while demonstrating that all security criteria are satisfied. To do that, we must understand the needs of the stakeholders better. In expressing system requirements and benefits, we need to start using the terminology of users, corporate/government purchasers, and regulatory agencies. Stakeholder Needs and Requirements is relevant here. The company needs to quantify expected ROI for investing in its products.
  • System Realization addresses our broader V&V concerns. Reliability measures on system performance need to be demonstrated. We were unaware of standard models and measures for system reliability — now staff must develop tests to quantify important attributes. We may want to model reliability and system adherence to regulations using a form of Model-Based Systems Engineering (MBSE). We can learn more about this from the references.
  • Part 5: Enabling Systems Engineering makes a convincing case that having the right people for a new systems engineering culture is critical. We should probably hire a systems engineer or two to augment our engineering department expertise.

Jose is now better prepared to adapt his processes for new system lifecycles and environments. He can quantify the business case to potential clients for his technology innovations, the initial morass of agencies and regulations is now finite, he can make inroads into new markets, and simultaneously strengthen his staff for the long term enterprise.

Vignette: Mechanical Engineer

Cindy Glass is a mechanical engineer with experience in the petroleum industry, primarily working with large oil extraction equipment in the field. Now she is tasked to help manage the development of new offshore oil platforms with robotic technology, computer networks and broader systems considerations. This calls for incorporating systems engineering principles from day one.

Some of the drilling operations will be done remotely with unmanned underwater vehicles (UUVs). Safety has always been a major concern but now cyber security also is. Environmentalist hackers, opposing nations or others may try to cause havoc by taking control of the remote vehicles and other operations. Unfortunately she is completely new to software system implementation. Cindy realizes there are many more dimensions of system constraints and engineering disciplines to deal with.

Previously she implemented minor design changes in existing equipment with automation and safety guidelines already in place. Now she is dealing with the earliest stages of the platform lifecycle starting from scratch. She already understands mechanical tradeoffs between different types of rigs and drilling materials, but now has to incorporate system security and new environmental constraints in her system analysis. System Realization gives her references for system design with many ilities.

The project lifecycle will require concurrent engineering of platform sub-components while evaluating technology opportunities, understanding the needs of all stakeholders inside and outside the company, and progressing through increasingly detailed prototypes, working slices of software, system specifications, designs, plans, business cases, security and safety analyses of the platform architecture and its operations.

Part 3: SE and Management also describes how her management activities will have to be rigorous and consider the interfaces between the engineering specialties. The section on Planning gives her detailed advice for starting out. The full project plan will call for a broad set of integrated management and technical plans. Conception through Operations will have to involve all the disciplines.

Since she is new to working on software projects and with software engineers, she reads The Nature of Software and Ten Things a Systems Engineer Needs to Know about Software Engineering. She also knows now about the SWEBoK for references on software engineering. She needs some guidance on managing a software team and studies Ten Things a Systems Engineer Needs to Know about Managing a Software Team.

It is clear that Systems Engineering and Software Engineering will be particularly intertwined. Among other things she is reminded to include security specialists at both the software level and the systems level from the beginning.

Cindy now appreciates the broader range of system constraints and thus engineering disciplines she needs to work with. The references in the SEBoK will be consulted throughout the architecting, design, development and deployment of the new platforms.

Summary

The SEBoK provides insights and guidance concerning systems engineering principles for other kinds of engineers and related technical disciplines. These engineers will benefit from the knowledge areas highlighted in this use case. The SEBoK gives pointers to major references for other engineers to become more interdisciplinary and consider additional aspects in their job. Thus they become more valuable to their employers and society.

References

Works Cited

Abran, A., J. W. Moore, P. Bourque, R. Dupuis, and L. L. Tripp. 2004. SWEBOK: Guide to the Software Engineering Body of Knowledge, 2004 version. Los Alamitos, CA, USA and Tokyo, Japan: IEEE Computer Society Press.

Primary References

None.

Additional References

None.


< Previous Article | Parent Article | Next Article >
SEBoK v. 1.9.1 released 30 September 2018

SEBoK Discussion

Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.

If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.

blog comments powered by Disqus