 |
Arete Industries LLC |
| Home |
| Contact Us |
| Who we are |
| Client Profiles |
| Software Design |
| COM / DNA |
| Microsoft .Net |
| Scripts |
| Software Design Principles |
| Software design is the step in the software development process prior to construction. It is the step where you think about what you are going to build, what tools or prebuilt components you need, what components you need to build, and how it all fits together. The amount of time spent on the design of the software depends on the complexity of the software. Leaping into the construction, or code development, phase before the actual problem is well understood is the cause of more software project failures than any other reason. Many developers, unfortunately, spend less than an adequate amount of time and effort doing design. This is perhaps because developers as a rule are far more proficient in coding than in Business Analysis. |
 |
| Business Analysis |
|
Arete Industries Chief Developer, Mr. Charles Bretana Jr, is not only a highly
proficient developer and systems architect, he is an experienced business systems analyst
with the education (M.B.A.) and expertise to analyze, model, and understand your business,
as well as your information technology problem.
Mr Perry Herman has extensive account management experience with numerous clients. He personally managed the recent Artists Guild labor management dispute from t's inital inception, through to the final disposition. |
|
| Unified Modeling Language (UML) |
|
Unified Modeling Language is is an object oriented (OO) modeling technique that
evolved as a result of the combined work of James Rumbaugh, Grady Booch and Ivar Jacobson,
each of who had their own OO modeling notation. The Object Management Group (OMG)
adopted UML as a standard for software modeling in late 1997.
UML is now the defacto standard for software modeling and design.
There are two important reasons why using a Modeling Language is crucial. First, the model provides a blueprint for developers so they know exactly what they need to build and for project managers so that they can precisely estimate the cost of a given project. Secondly, and more importantly, UML is the bridge between technical developers and their non technical users; UML allows the developers to get a precise understanding of the exact requirements that the users have for the system being built. Determining system requirements using the UML Model is done using Use Case analysis, and Process FLow Diagrams. |
|
| Use Case Analysis |
| Use Cases are... |
|
| Process FLow Diagrams |
| Process FLow Diagrams are... |
|