• Introduction
• Requirement Management
• Software Modeling
• UML
• Design Pattern
• Software Architecture
• Risk Management
• Outsourcing

What is UML?

• visualizing
• specifying
• constructing
• documenting the artifacts of a software intensive system
• This is primarily a graphical communication mechanism for developers and customers
• The main purpose of UML is to support communication about the analysis and design of the system being developed
• Support the movement from the problem domain in the "world" to the solution domain in the machine
• Reverse engineer your code with a UML tool to see how your code looks in UML
• Unified Modeling Language comes from Rumbaugh, Booch, and Jacobson (the three amigos) who combined efforts to standardize on one modeling language
• Two views of the same system
  • one view has diagrams
  • source code is another view

Motivation for Modeling Language

• If a team is not able to communicate efficiently, there end product won't be as good as it should be.
• If that development team can't build an application that meets the needs of the end user, it will be a complete failure.
• Once the application has went through the development process, the team members will be able to reference the model and look for any changes that may be needed. In this end, this creates a system that is much more efficient.
• In addition to this, the development time will be greatly reduced.
• In a day and age where communication has become more important, and where development teams work on an international scale, it has become more important to use a powerful language that makes communication seamless and efficient.
• If you're putting together a team to develop an application, and they all live in remote locations, the Unified Modeling Language is a tool that is virtually indispensable.
• Requirements-Ill-Defined Because the starting point for many projects is ill defined, Many times, the only requirements you're given are an existing application or just a sketchy idea in someone's head.
• Solidify RequirementsYou need a well-formulated plan to solidify the requirements and gain concurrence with your client.
• Known-Unknown
  • Every project should start with a list of knowns and unknowns of your project.
  • This brainstorming effort should result in a substantial list of issues that require resolution.
  • These issues form the basis of your initial interviewing sessions where the vision and scope of the project are agreed upon, and the process of identifying risks is begun.