There are times and cases when a use case using simple text, cannot properly describe a process. In those cases, look to supplement the Use Case to make it easier to understand the process.
Activity diagrams can be used to show the workflow of a process the the user/system should take.
A Swimlane diagram can be used when you have multiple interfaces so you know which element should be performing which task.
UML Models to Supplement Use Cases was originally found on Access 2 Learn
Assistant Professor
Walter Wimberly is an Assistant Professor at a regional college in Tennessee, teaching Computer Science in the Software Engineering track. He works as a student advisor, oversees curriculum changes, develops new courses, and manages the advisory panel.
Walter taught full time for about 7 years, before going back into “industry” as a full stack Software Developer for a dozen years. There he focused on web based projects coding in JavaScript/jQuery and utilizing the Bootstrap CSS Framework on the front-end, and coding in PHP, ASP/ASP.Net, SQL on the back-end.
Since he loves teaching, he taught as an adjunct web and digital media classes for eight (8) years, while working in industry, and has since returned to teaching full time.
He has been married for over 25 years, and is father to several special needs boys. As such, he is working on some projects to help others who have special needs to be self-sufficient, and support the care givers of those with special needs. Check out his Autism blog for more info.
Each software engineering action (Communication, Planning, Modeling, etc) can be represented by a task set, or series of tasks to do to complete the action. Depending upon the size of the project, and the needs of the project, the number of task could vary. When doing initial communication, a small project with a single stakeholder…
Best practices make for a more likely used and well rated app. Many apps are never used after the first few days – so using best practices will help increase the chance of it being used. Identify your audience. Know what they need, and how they want/plan to use it. Design for context of use….
A design pattern can be characterized as “a three-part rule which expresses a relation between a certain context, a problem, and a solution” [Ale79] For software design, context allows the reader to understand the environment in which the problem resides and what solution might be appropriate within that environment. A set of requirements, including limitations and constraints, acts as…
Security requirements are nonfunctional requirements that strongly influence the architectural design of software systems. Security requirements and other requirements can conflict with one another. A common example is that security and usability are often at odds with one another, and a balance between the two must be found. Therefore you have to determine how secure do you…
If you were to ask someone on the street, what is quality – do you think they could answer? What do you think they would answer? Would it be the same are yours? Quality is a fairly complex topic, that means different things to different people. It is something that can be recognized, even if…
Some things are easy to identify as a class. For example, if you look around the room, you can find lots of physical objects which can be made into classes. However, in a software environment, this may not always be as easy to identify. So look at the following questions to start to identify what…
