| Introduction | Technical Web Site of Leslie Munday (Available for consulting work) If you see any analysis or SDLC process material of interest, do not hesitate to contact me. My rates are flexible (and a lot cheaper than IBM or Microsoft). |
|---|---|
| Book | A book of the material is coming together. If you are looking for the Chapters that are currently available, click on the 'Blog' link to the left. |
| Purpose | The purpose of this site is to share UML and related
software development material that has been created or worked on by
Leslie Munday. During my 20+ years experience in business and systems analysis, I have created a lot of presentations and written many example work products. Much of my past work is uploaded to this site and it is all free to download. |
| Overview of the material |
If you take each course in the
recommended sequence, you will have gained knowledge of a software
requirements
development lifecycle. The lifecycle is based on RUP, from Business Modeling through to the Analysis
part of the Analysis and Design discipline. Most of my experience is
with the Rational Analyst Studio Suite. Where the material introduces
tools into the process, these will be the Rational tools. There is no
reason why the material could not be configured to work with other
tools. I have followed these same processes using Paradigm Plus, Visio and
even Excel. A lot of the links do not exist at this time (even though the material exists). That is because this material will never be complete, and the 'under construction' sign will never go away. This is the culmination of 20 years work and in 20 years time it will be the culmination of 40 years experience with analysis. |
| Organization | The material
on this site is organized by the RUP discipline that it falls under. The
links to the left of each page will open the discipline page and take you
directly to the material. The following links will take you to the
discipline page containing the link to the material. Clicking on the discipline button, at the top of the page will open the page containing the material for that discipline. |
| RequisitePro models | This zip file contains three ReqPro projects that were used to take the slide shots in the following documents. |
| Working with styles and properties | This presentation is concerned with selecting the document styles and properties that will be used within document templates. |
| Vision template | This is the vision document template. |
| Business use case template | This is the business use case document template. |
| Using the business use case template | This presentation guides you through the sections of the BUC template. |
| A notation for activity diagrams | This presentation defines a notation for diagramming activity diagrams. |
| Introduction to ReqPro | This presentation contains an overview of the RequisitePro. |
| Administering ReqPro | This is an administration guide to managing ReqPro projects. |
| Maintaining a glossary with RequistePro | This presentation describes how to use a glossary with ReqPro. |
| The requirements management plan template | This is the standard RUP template for a requirements management plan. |
| Managing requirements with a RMP | This presentation teaches you how about the requirements management plan. |
| Managing business requirements with ReqPro | This presentation explains requirements are managed within ReqPro. |
| Business modeling discipline overview | This presentation describes how to model business use cases with Rational Software Modeler. |
| The application use case template | This is the application use case template. |
| Using the application use case template | This presentation teaches you about AUC document. |
| Managing AUC requirements with ReqPro | This presentation describes a method for managing application use cases within ReqPro. |
| Moving from the BUC to the AUC | This presentation explains how to tranform your BUCs into system requirements. |
| The project lifecycle | This presentation gives an overview of the software development lifecycle. |
| Use case storyboard template | This the template for a use case storyboard. |
| Using the use case storyboard template | This is a short presentation about how to complete a storyboard document. |
| What is a state transition diagram? | This presentation describes a notation for state transition diagrams |
| Working with class diagrams | This presentation shows how to create classes that trace to use cases. |
| Realizing the use case | This presentation explains a method for realizing use cases with sequence diagrams. |
| Contact Information |
|
| Footnote 1 | The colors used for the disciplines are the same colors assigned to each of the disciplines by the Rational Unified Process. |
| Footnote 2 | Why 'application' use case? I have had many discussions about the meaning of the terms 'Business Use Case' vs 'System Use Case' vs 'Use Case', both with people at Rational and with Rational customers. I refuse to use the term 'use case', because it is not clear whether this refers to a BUC or a SUC, but I noticed a certain reluctance for some people to use the system use case abbreviation, SUC. For this reason I looked to find a replacement word for 'system', and came up 'application'. Not only is the AUC acronym more acceptable, but I believe that the term 'application' is more appropriate than 'system'. When working with the Requirements discipline I think of a system as a machine that includes both hardware and software. When you follow the guidelines in this material, in the Requirements discipline you are writing a use case for just the software, not the hardware or manual process. To me, 'application' seems more appropriate than 'system', because it says, this use case is describing the software for a single application. |
| Footnote 3 |
The material encourages the original 6 RUP best practices: Develop Iteratively - describes a use case approach, whereby each use case may be developed independently of each other. Manage Requirements - describes using RequisitePro to manage requirements. Use Component Architectures - describes organization by packages and classes. Model Visually - describes various UML diagram notations and where the diagrams may be best used. Continuously Verify Quality - describes analysis techniques for verifying the requirements are correct. Manage Change - describes using MS SharePoint to manage the files that are created and used by the process. |