Click here to close now.


IBM Cloud Authors: Jason Bloomberg, Liz McMillan, XebiaLabs Blog, Elizabeth White, Carmen Gonzalez

Related Topics: IBM Cloud

IBM Cloud: Article

The Six Principles of Systems Engineering

IBM's Rational Rules Developed Over 10-Year Period

IBM Rational's six principles of systems engineering are a set of high-level systems development guidelines derived from the careful analysis of successful, complex systems development engagements over the past ten years.

Although they are neither comprehensive nor mutually exclusive, they serve to highlight key areas of focus for organizations interested in quickly building expertise in complex systems development. They also serve as a "measuring stick" for assessing potential problem areas and the root causes underlying symptomatic project deficiencies or failures. It is well-known and accepted that function, schedule, and cost are three key and mutually dependent aspects of project management -- make a change to one, and the effects often ripple through the other two.

A similar relationship exists in product and program management for complex systems development. As shown in Figure 1, the three key aspects are:

  1. Systems architecture
  2. Organizational structure, including the systems development infrastructure
  3. Process, including workflows, best practices, and the like
These aspects collaborate to help achieve the following:

  • "Build the right system and build the system right"

    Architecture focuses on building the right system and model-driven use-case based architectural decomposition lays the foundation for building the system right. Why is architecture singled out? Because it provides the foundation on which the system is ultimately constructed. The choices made in selecting the system's architecture become a lasting legacy - either good or bad.

    Here's a transportation example: The basic architecture used for centuries in building roads or other transportation elements (like rail tracks) was basically point-to-point (the shortest distance between two points can be considered optimal since it minimizes the road length and one would assume maximizes time to travel efficiency). Simple enough, but there was always at least a physical constraint: the terrain, which forced the path to avoid obstacles. There were also other potential constraints such as "hostile" territory or political boundaries.

    In any case, roads were built and paths crossed somewhat haphazardly. Move forward to the 20th century. Population growth generated additional constraints - namely street lights or traffic signs to optimize the flow of traffic through intersections. These are somewhat problematic on roads architected in the point-to-point avoid obstacle approach, especially where more than two roads intersect. A clearly "better" architecture has proven to be laying out roads in rectangular grids. This architecture and the many implementations are much easier to control from a signaling and traffic flow perspective.

    So build the right system and build it right - making it robust (scalable, extendible, easy to maintain, easy to use, and so on).

  • "Do the right things, and do the things right"

    The systems development framework focuses on defining the right things to do throughout the product lifecycle to optimize business value and return on investment and best practices, processes/supporting tools and governance (requirements, quality, change, configuration, and program/project management) focus on ensuring things are done right.

  • "Apply the right resources, and apply the resources right"

    "Doing" and "building" are action verbs; they require resources to perform the "doing" and the "building". The most significant enterprise resource is people, followed by supporting infrastructure. Acquiring, motivating, and retaining skilled personnel applies the right resources, and aligning the organization appropriately to optimize communication, collaboration, and effort applies the resources optimally. A sound enterprise infrastructure (including IT equipment and software) is one key aspect in ensuring the resources are applied optimally, once again maximizing business value and return on investment

    The six principles of systems engineering address all three aspects described above. The three technical principles (noted below) focus on architecture and the derivation of system models, while the remaining principles provide the complementary infrastructures and workflows needed to optimize the technical development environment.

    The six systems engineering development principles are:

    1. Decompose systems, not requirements (technical).
    2. Enable both separation and integration of "key systems development" concerns (technical).
    3. Specifications flow up and down the architecture (technical).
    4. Systems and components collaborate; so should development teams.
    5. Development organizations should reflect product architectures.
    6. Base the "development" lifecycle on removing risk and adding value.
    Let's examine each of these principles, initially from a generic systems engineering view, and then specifically in the context of joint hardware/software development.

    Decompose systems, not requirements
    Since systems and software engineering principles and methods have been written about, discussed, and applied in countless cases, one might think that development teams have a common understanding of such terms as "system" and "systems engineering." Unfortunately, this is not the case; neither across enterprises within a specific industry nor across the product and functional domains within an engineering development community in a single enterprise.

    According to INCOSE (the International Council on Systems Engineering), systems engineering is2:
    An interdisciplinary approach and means to enable the realization of successful systems. It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, and then proceeding with design synthesis and system validation while considering the complete problem:

    • Operations
    • Performance
    • Test
    • Manufacturing
    • Cost and Schedule
    • Training and Support
    • Disposal
    A system is a group of interacting, interrelated, or interdependent elements forming a complex whole, which provides a set of services that are used by an enterprise to carry out a business purpose (mission). System components consist of hardware, software, data, and workers3. Put simply, a system is a complex entity that provides some tangible result of value. Systems engineering is a disciplined approach that helps us examine desired results and determine what can satisfy them. It also helps us determine how to do this within a set of business-critical constraints (cost, schedule, testing parameters, ease of manufacturing, and so on). The "what" is the system, the "how" is the functional requirements, the "business-critical constraints" are the supplementary requirements, and the "desired results" are products of use cases.
  • More Stories By Murray Cantor

    Murray Cantor is a member of the IBM Rational CTO team, taking the lead for Governance and Systems. Cantor formerly lead the IBM Rational field services group, promoting and extending Rational best practices, and working closely with customers on innovative ways to build and deliver systems more efficiently.

    More Stories By Gene Roose

    Gene Roose is a senior systems engineering consultant for IBM Rational, concentrating on model-driven systems development methods. He assists clients with solution analysis and design, architectural derivation and validation, and overall project management.

    Comments (0)

    Share your thoughts on this story.

    Add your comment
    You must be signed in to add a comment. Sign-in | Register

    In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

    @ThingsExpo Stories
    Today air travel is a minefield of delays, hassles and customer disappointment. Airlines struggle to revitalize the experience. GE and M2Mi will demonstrate practical examples of how IoT solutions are helping airlines bring back personalization, reduce trip time and improve reliability. In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect with GE, and Dr. Sarah Cooper, M2Mi's VP Business Development and Engineering, will explore the IoT cloud-based platform technologies driving this change including privacy controls, data transparency and integration of real time context w...
    The buzz continues for cloud, data analytics and the Internet of Things (IoT) and their collective impact across all industries. But a new conversation is emerging - how do companies use industry disruption and technology enablers to lead in markets undergoing change, uncertainty and ambiguity? Organizations of all sizes need to evolve and transform, often under massive pressure, as industry lines blur and merge and traditional business models are assaulted and turned upside down. In this new data-driven world, marketplaces reign supreme while interoperability, APIs and applications deliver un...
    Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome,” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
    Electric power utilities face relentless pressure on their financial performance, and reducing distribution grid losses is one of the last untapped opportunities to meet their business goals. Combining IoT-enabled sensors and cloud-based data analytics, utilities now are able to find, quantify and reduce losses faster – and with a smaller IT footprint. Solutions exist using Internet-enabled sensors deployed temporarily at strategic locations within the distribution grid to measure actual line loads.
    The Internet of Everything is re-shaping technology trends–moving away from “request/response” architecture to an “always-on” Streaming Web where data is in constant motion and secure, reliable communication is an absolute necessity. As more and more THINGS go online, the challenges that developers will need to address will only increase exponentially. In his session at @ThingsExpo, Todd Greene, Founder & CEO of PubNub, will explore the current state of IoT connectivity and review key trends and technology requirements that will drive the Internet of Things from hype to reality.
    The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data shows "less than 10 percent of IoT developers are making enough to support a reasonably sized team....
    You have your devices and your data, but what about the rest of your Internet of Things story? Two popular classes of technologies that nicely handle the Big Data analytics for Internet of Things are Apache Hadoop and NoSQL. Hadoop is designed for parallelizing analytical work across many servers and is ideal for the massive data volumes you create with IoT devices. NoSQL databases such as Apache HBase are ideal for storing and retrieving IoT data as “time series data.”
    The IoT market is on track to hit $7.1 trillion in 2020. The reality is that only a handful of companies are ready for this massive demand. There are a lot of barriers, paint points, traps, and hidden roadblocks. How can we deal with these issues and challenges? The paradigm has changed. Old-style ad-hoc trial-and-error ways will certainly lead you to the dead end. What is mandatory is an overarching and adaptive approach to effectively handle the rapid changes and exponential growth.
    Today’s connected world is moving from devices towards things, what this means is that by using increasingly low cost sensors embedded in devices we can create many new use cases. These span across use cases in cities, vehicles, home, offices, factories, retail environments, worksites, health, logistics, and health. These use cases rely on ubiquitous connectivity and generate massive amounts of data at scale. These technologies enable new business opportunities, ways to optimize and automate, along with new ways to engage with users.
    The IoT is upon us, but today’s databases, built on 30-year-old math, require multiple platforms to create a single solution. Data demands of the IoT require Big Data systems that can handle ingest, transactions and analytics concurrently adapting to varied situations as they occur, with speed at scale. In his session at @ThingsExpo, Chad Jones, chief strategy officer at Deep Information Sciences, will look differently at IoT data so enterprises can fully leverage their IoT potential. He’ll share tips on how to speed up business initiatives, harness Big Data and remain one step ahead by apply...
    There will be 20 billion IoT devices connected to the Internet soon. What if we could control these devices with our voice, mind, or gestures? What if we could teach these devices how to talk to each other? What if these devices could learn how to interact with us (and each other) to make our lives better? What if Jarvis was real? How can I gain these super powers? In his session at 17th Cloud Expo, Chris Matthieu, co-founder and CTO of Octoblu, will show you!
    SYS-CON Events announced today that ProfitBricks, the provider of painless cloud infrastructure, will exhibit at SYS-CON's 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. ProfitBricks is the IaaS provider that offers a painless cloud experience for all IT users, with no learning curve. ProfitBricks boasts flexible cloud servers and networking, an integrated Data Center Designer tool for visual control over the cloud and the best price/performance value available. ProfitBricks was named one of the coolest Clo...
    As a company adopts a DevOps approach to software development, what are key things that both the Dev and Ops side of the business must keep in mind to ensure effective continuous delivery? In his session at DevOps Summit, Mark Hydar, Head of DevOps, Ericsson TV Platforms, will share best practices and provide helpful tips for Ops teams to adopt an open line of communication with the development side of the house to ensure success between the two sides.
    SYS-CON Events announced today that IBM Cloud Data Services has been named “Bronze Sponsor” of SYS-CON's 17th Cloud Expo, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. IBM Cloud Data Services offers a portfolio of integrated, best-of-breed cloud data services for developers focused on mobile computing and analytics use cases.
    SYS-CON Events announced today that Sandy Carter, IBM General Manager Cloud Ecosystem and Developers, and a Social Business Evangelist, will keynote at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA.
    Developing software for the Internet of Things (IoT) comes with its own set of challenges. Security, privacy, and unified standards are a few key issues. In addition, each IoT product is comprised of at least three separate application components: the software embedded in the device, the backend big-data service, and the mobile application for the end user's controls. Each component is developed by a different team, using different technologies and practices, and deployed to a different stack/target - this makes the integration of these separate pipelines and the coordination of software upd...
    Mobile messaging has been a popular communication channel for more than 20 years. Finnish engineer Matti Makkonen invented the idea for SMS (Short Message Service) in 1984, making his vision a reality on December 3, 1992 by sending the first message ("Happy Christmas") from a PC to a cell phone. Since then, the technology has evolved immensely, from both a technology standpoint, and in our everyday uses for it. Originally used for person-to-person (P2P) communication, i.e., Sally sends a text message to Betty – mobile messaging now offers tremendous value to businesses for customer and empl...
    "Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
    WebRTC converts the entire network into a ubiquitous communications cloud thereby connecting anytime, anywhere through any point. In his session at WebRTC Summit,, Mark Castleman, EIR at Bell Labs and Head of Future X Labs, will discuss how the transformational nature of communications is achieved through the democratizing force of WebRTC. WebRTC is doing for voice what HTML did for web content.
    Nowadays, a large number of sensors and devices are connected to the network. Leading-edge IoT technologies integrate various types of sensor data to create a new value for several business decision scenarios. The transparent cloud is a model of a new IoT emergence service platform. Many service providers store and access various types of sensor data in order to create and find out new business values by integrating such data.