Partial Inception Documents
MetriK SRS
MetriK Use-Cases
As I go through the inception phase and start developing these artifacts, I am realizing that I only have so much time and resources to spend on each one. Thus, you will notice that in some areas there are some deficiencies. In later iterations these "holes" will be filled and in some cases when I feel that I have completed enough to continue, they will be omitted. I also made decided that several of the use-cases should be composite to speed things up and cut down the complexity that could occur if each use-case was a stand alone and “fully dressed.”
The most important thing is not that the documents are perfect, but that they help me to better grasp the overall architecture and requirements in general. It doesn’t help me to write down what I already know, but it does help me in the fact that I am broadening my knowledge of the requisite problem domains. I guess that is the essence of a software process derived from the UP school of thought.
Next up:
- Use Case Diagrams
- Glossary
- Design Model
- Implementation Model
- Architectural baseline (yeah)
- UML Package, class, and interaction diagrams
- Additional documents
- Software Architectural Document
- Current Schedule (I am behind on this)
I continuing with the metaphor of using a modified UP software process, I will likely create either abbreviated versions of these traditional UP artifacts and in some cases creating composite artifacts when I feel that it is necessary.