Welcome to our new site version. Your web page bookmarks may have changed, please search for pages by title to update them. Having problems ? Please try clearing your web browser cache and hard-reloading your web page first before contacting our webmaster.

How To Recogize You Have A Systems Problem

[document] Submitted on 12 February, 2017 - 23:06
Keywords recognizing systems problem systems problems

To determine whether you do have a system problem, you need to perform three tests. These tests will show if delays and cost overruns are arising for one or two reasons. The first could be because the components of the product don’t interface with each other as a system. This is analogous to putting together a child’s bike. If the parts in the box don’t fit, then you won’t have something that looks like a bike. The second could be due to incomplete requirements that went into building the components, which would result in a system not functioning as expected. In the bike example, even if the parts do fit, the bike may not work as intended. For instance, the bike doesn’t stop properly because the brakes don’t have proper contact with the wheels.

Metadata
Date published
UNKNOWN
Language of Attachment(s)
English
Replaced/Superseded by document(s)
Cancelled by
Amended by
File MIME type Size (KB) Language Download
How To Recognize You Have A Systems Problem.pdf application/pdf   80.34 KB English DOWNLOAD!
File attachments
Cover images
Organisation(s)
Defines standard
Visit also