Systems and Software Engineering

Welcome to
Systems and Software Engineering

Home

Retail Center
Industrial Office Park
Community Center
Search
Customer Service
Be Part of CassBeth

Merry Christmas & Happy New Year
Let there be peace and happiness
for all people in this new century






Great Christmas Carols and more. Just click and enjoy. Rudolph | Winter Wonder Land | Nutcracker | Hark The Herald Angels | Do You Hear What I Hear | Dance Of The Sugar Plum | Sleigh Ride 2 | Sleigh Ride | Silver Bells | Up On the Roof | Brasil

Christmas Backgrounds
Merry Christmas From Lizzy. santa and frosty at our house

christmas trees 640X512
christmas trees 800X640
christmas trees 300X240

Click ME ..... click ME!

NO! Click ME!

Available through January 7

Check out more technology stuff at
CassBeth Technology


The dilemma, how do you build software intensive systems that satisfy customer requirements and needs (these are not the same things) in a predictable cost and schedule effective manor. Coupled with this was/is the realization that if you actually develop something that really works, historically, the time and money spent was/is significant. So, how can you increase the productivity of the software development area primarily, and still deliver good solid software intensive systems.

The problem was actually noticed very early on in the computer era, dating back to the 50's. The approaches back in those days were not only viewed as a technical problem within the realm of computers and the yet to be defined computer science arena, but also a human problem. Many people and organizations proposed and tried using people with widely differing skill sets to develop software in the hope to find the right match between the person and the "software" tasks to be completed. The types of individuals considered were mathematicians, engineers, artists, linguists, and people familiar with the application. A good example is the US Air Traffic Control System, where IBM and the FAA concluded that it was more effective to train air traffic controllers in software development and maintenance, than to train technical types in the air traffic control application. The implementation of software was viewed as a relatively low skill production activity with tight controls and monitoring, as opposed to design. The common thought was that you could train someone to program in 6 months, but it would take someone 5 years to work through all the ATC controller jobs in the system. The work through was the key issue. It was believed that classroom instruction could never substitute for on the job experience ATC controller experience. There is a contrary view-1 and  contrary view-2 .

The ATC example is at the heart of this dilemma. In the early stages of the development of the current computer based Air Traffic Control System, there were significant problems with the system. The attempt was to introduce the digital computer into the system and add information management capabilities which were not present in the broad band system. For example, generate a computer symbol for the aircraft position instead of an analog smudge on the CRT. Tag the aircraft symbol with alpha numeric information, instead of using a grease pencil or plastic "shrimp boat" on the CRT surface. The goals however did not meet expectations when the system was initially delivered.

A classic example of the problems in the system were associated with flight plan processing and paper flight strips. A paper flight strip contains all the information associated with an airplane in flight. This includes departing and destination airports and the various legs of the flight. When the system was initially delivered, paper flight strips were printed at each position in  the facility, regardless of whether or not that position would ever come in contact with that flight. Further, if there was a change in flight plan due to a controllers clearance, the flight strips would be re-printed with the undated information. Sounded good to the techie's and management types responsible for cost and schedule. The problem was that paper was being generated everywhere. Imagine receiving information from 50 other positions, and you had to determine which ones to throw away. The system met the requirements, but failed miserably in the needs area. Bring in the domain experts, ATC controllers, and train them in software. It took 2 years to get the little flight strips to print to the proper location in a predictable manor. The tradeoff, 2 years work versus printing flight strips everywhere... Hummmm.

Fast forward to Yourden. Perhaps a process, that everyone understood, coupled with automated tools could be used against the software crisis. Fast forward from Structured Systems Analysis to language. The languages are all wrong. A strongly typed language that would enforce good programming techniques would address the crisis, Ada, that's the answer. Oops, our process is still not right. We need to track requirements. A relational database is what is needed, because after all its the system that is not meeting requirements, and we just missed it in the paper mountain of specifications. Fast forward again, you know that SSA stuff ,it really should be Objects, and we need tools for OOA/OOD, that is the answer...

You don't need to be a rocket scientist to see a trend here. Even an air traffic controller can detect this pattern. Obviously developing software intensive systems is hard, but, you know what, there are many of them out there, they work, we are becoming more dependent upon them, because they work, and it is obviously possible to do this stuff and still survive. So what is really going on?

In my humble opinion, the successful systems, are the ones that applied basic engineering principles that have been around for a very long time, at least since the Romans were building roads.

  • Understand what you are trying to do. The answers are irrelevant. Its the questions that are key. Are you asking the right questions. If you are afraid to have an organization that asks questions, then stop right here and do only "build to print jobs". Don't even attempt to enter this world.
  • Counting requirements is like counting the number of angels on the head of a pin. The Air Traffic Controllers loved that analogy, "engineers love to count the number of angels on the head of a pin, the pin heads". Well they are right. It is the key requirements that drive your system. Find the cost and technology drivers and list them, every single day, and make sure everybody sees them including your customer and most junior employee.
  • Once you have a list of questions and the key requirements, then the analysis needs to start. I'm sorry, but I don't know of any systems and software engineering tool that allows an analyst to address the really hard questions and requirements in a creative manor. The introduction of the PC with drawing packages, spread sheets, and custom software from thousands of vendors are the tools of the analyst.
  • What is possible today, that was not possible in the past for the most part, is the ability to prototype the users interaction with the system. Prototype it. Eventually you will need all the requirements, not just the key requirements. A prototype, if complete, will surface all these requirements. The key here is a complete prototype, not a sales pitch. You are already under contract. The sooner you show the prototype to your customer the better. This by the way is traditional engineering. Everyone builds physical models, except for software types... that is a major problem in the profession.
  • If you are developing algorithms, move them from the models to the prototype environment as soon as possible.

Now for the big question. Should you use software and system engineering tools. The second big question is, which software and system engineering tools should you use in your activity. The early dream of the tool pioneers, the large aerospace companies, was to develop an end to end software factory based on tools. Press a button anywhere in the tool and see the associated code, requirements, data flows / objects, test plans, test results, analysis, models, information products, and anything else that makes up the job. The goal being to see the ripple effects as the system is modified over the years of operation. Does anyone have such a capability, no. The closest vendors appear to be associated with the software tool products. Its possible that the Internet may achieve the original goals of the large aerospace companies. For further information:

Status Quote

Systems Engineering: A Tutorial
Systems Engineering Home Page
Resources: SYSTEMS ENGINEERING SITES
Internet Resources
University of Virginia, Department of Systems Engineering
Requirements Management Technology Overview
INCOSE Tools Working Group Report
Tools Database Working Group: Tools Taxonomy
INCOSE Tools Database Working Group
INCOSE

Sw Perspective

Rational Software Corporation
Aonix Home Page, Application Development Tools for Business Critical Development
Bachman Information Systems and Cadre Technologies Merged to form Cayenne Software, Inc.
Welcome to SELECT Software Tools Home Page

Sys Perspective

Welcome to Vitech Corporation.
Welcome to Vitech Corporation.
QSS Requirements Management Requirements Engineering Systems Engineering
Chipware.com
TD Technologies, Inc.- "The Leader in Industrial Strength Groupware"
Compliance Automation, Inc.
XTie-RT Requirements Tracer, At last...affordable requirements management for everyone!
Foresight System Design Automation

Modeling

Welome to Imagine That, Inc.
Welcome to Alta!

Back


There is more to life then all this techie stuff. You are burning out half of your brain. Before it is too late, give it a rest and feed the other half of your brain with a visit to a wonderful sane cyber shop.


LinkExchange

LinkExchange Member Free Home Pages at GeoCities



Technologies
Copyright © 1997 All Rights Reserved.


Top of Page

.

CassBethVator™
Mall Floor Plan
CassBeth Portal



CassBeth Malls Faster Access ElizAndra
FredsSpot
OuterSpaceShopper
GiftsToHumanity
MartianShopper
EarthlingsUnited


Clothes & Jewelry
Clothes Galore
allé Fine Jewelry
Shoes For All
Womens Clothes
Mens Clothes
Kids Clothes
Accessories Wazzo
Old Navy - Target - Nordstrom - Lands' End - Gap - etc


Other Shops
Toys Games Galore
Video Games
Porcelain Dolls
Bears

Tools & Home Improvement
Gardening
Gourmet Cooking
Sporting Goods

Electronics Galore
MP3 Internet Music Players
DVD Players
Digital Cameras to Film
Camcorders
VCRs
CD Players
Nintendo Sony Playstation Sega
Office Supplies
Computers Printers Scanners
Software

Music CDs
DVD & VHS Videos
Hollywoods Greatest Movies
TV Shows
Dr Who Videos
Alien and UFO Media
Red Dwarf Videos
Star Trek Videos
Book Store
University Books
College SAT Prep Books

Cellular Phone Needs
Photography
Holiday Gifts
Electric Trains
BEARS
Weird Surveys
Travel Help & Specials
Stock Investing
FREE Greeting Cards
Stained Glass
Tiffany Stuff
Limoges Collectibles
Russian Collectibles
Button Dolls


General

Cassbeth Home
Shop Entrance
Search
Order Now
Order Guide
Info Kiosk


Services

Customer Service
Join Cassbeth
CassBeth Cyber mall Software
Site Map


Find a book, movie, DVD, CD, and other stuff

All Products Books Popular Music Classical Music DVD & Videos Toys & Games
Electronics Software Tools & Hardware Lawn & Garden Kitchen

In Association with Amazon.com

Star Wars Episode I - The Phantom Menace Hear My Cry Sonique Creator Genesis - The Lamb Lies Down On Broadway You


.

v 1.2 7/23/2000 19:30:48


Copyright © 2000 All Rights Reserved.