Why model software?

We model software in order to achieve a high level of quality from the finished product.

We could compare the process of software building to that of building with Lego blocks. Watch a child attempting to build a castle. He or she probably goes right ahead without looking at the instructions, starting with the larger pieces and then fitting the smaller blocks into the gaps.

Many software projects start using the very same technique. Work on the large, simple structures first, then move on to the more complex parts later. But perhaps at the end of the exercise, when the castle is about to topple, someone remembers the twenty-page manual with step by step procedures and diagrams that would have saved a lot of pain -- and probably also saved the project.

With the introduction of more intuitive technologies, thorough design, analysis and documentation has perhaps never been more vitally important.

Why model Use Cases?

Use Cases are the starting point for designing a new system and provide the highest form of detail about the system. Use Cases help us decide who will use the software and what they will do with it.

Use Case diagrams are also the point of reference for more complex UML models such as Activity and Class diagrams.

How we can help ...

We help you create UML specifications, requirements and technical documentation.

We have templates for the collection and recording of formal requirements and the expertise to provide you with strong technical documentation on all aspects of system development.

 

Want to know more?

contact us: @Renfield Communications