In-House Development

In-House Development

So how does a Systems Engineer help an organization think about getting In-House Development under control. You first define the subject system. In this case there are two. The first is the system to be developed or the "company" while the second is the system to develop. It is the "Development System".

The Systems Engineer helps figure out what is to be done for the company and then who will do it and when.


In a diverse organization or system, you need to find the stakeholders. Having identified the stakeholders it is important to identify their needs. Features are derived from needs and assigned to components of a logical architecture. Various programs or projects are defined by circling parts of the domain. Transactions, use cases and scenarios are used to model the interactions of users with the various systems. A classic SE process is used to define and audit artifacts. This will help you begin a domain diagram that shows the existing and desired systems of the company that must be procured, refined or integrated.


These are attached to a project management plan. Depending on the scope of the projects, A project Review Board or an Executive board is formed to monitor the overall process. Various project managers monitor the project schedule and facilitate the resolution of roadblocks. Part of each plan is an overall effort estimate. These estimates are used to allocate budgets and determine staffing plans. With a small staff all the projects are scheduled sequentially. With a larger staff some parallelism can be employed. How much parallel development is possible depends on how partitionable the individual projects are.

Back | Next | Scaling to Small Business

Copyright Spidel Tech Solutions, Inc. 2004 All Rights Reserved.  Updated: 7/9/2009 12:22:45 AM Idx: 1765 Site Design STS

This site is the home of Spidel School of Design
Please visit the Spidel Tech Blog.