What is the difference between systems analysis and systems design?
The difference between systems analysis and system design is that system analysis is used to determine what the new system do. On the other hand, systems design is used to determine how the new system should be built this involves its structure and architecture.
- How do a use case diagram and a class diagram drive the system development process?
The use case diagram describes the processes of the new system and the class diagram explains the data of the new system. Each system consists of processes and information, therefore, the two diagrams describes what is to be done.
- How does an activity diagram help in user-interface design?
It shows the interactions between a user and the system. Those interactions must be supported by the user interface.
- What new information is provided in a design class diagram (more than a class diagram)?
To begin with, a design class diagram is an extension of a class diagram and it demonstrates how the attributes become data fields with type information. Moreover, it also identifies the methods of a class and shows which classes have visibility to other classes to access their methods.
- What is the iterative approach that involves completing and deploying part of an application over a few iterations and then completing and deploying another part of that application after a few more iterations?
This is known as incremental development. A walking skeleton is a variation of incremental development that builds the entire structure.
- What is a system development methodology?
A methodology is an entire set of guidelines and procedures that are used to develop a new system. It includes what modeling approach to use, what tools, what techniques to do analysis and design and programming. Therefore, a methodology gives the guidelines for the entire development process.
- What are three diagrams created by the structured approach?
- Data flow diagram
- Structure chart
- Entity Relationship diagram (ER)
- What are the main object-oriented techniques?
Object oriented analysis – OOA
Object oriented programming – OOP
Object oriented design – OOD
- What are the 11 Agile modeling principles?
These principles are:
- Developing software as your primary goal.
- Enabling the next effort as your secondary goal.
- Minimizing your modeling activity—few and simple.
- Embracing change, and change incrementally.
- Modeling with a purpose.
- Building multiple models.
- Building high-quality models and get feedback rapidly.
Focusing on content rather than representation