What is your impression of Agile as a process, and UML as a documentation system?
In my point of view,the iterative waterfall model has been popular but there is a lot of problems in the iterative waterfall model.Some of them are:-
1)Difficult to adopt change requests
2)Incremental delivery is not supported
3)Phase overlap not supported
4)Error correction is very expensive
5)Limitation to customer interactions
6)Heavy documentation
7)Not support for risk handling.
The word Agile is an umbrella term referred to a group of processes that is used for the development of the software.
Agile models:-
1)Crystal
2)Atern
3)Scrum
4)Extreme programming
5)Lean development 6)Unified process
Most popular models are Scrum and Extreme programming,At a time,only one increment is planned and developed and give it to the customer.The agile model adopts an iterative approach.
Main points in agile model is :-
1)working software over comprehensive documentation
2)Frequent delivery of incremental versions of software to the customer
3)Requirements change requests are supported.
4)Having competent team members and improving employee interactions.
Mainly agile model usually uses pair programming.
It doesn't recommend use prototypes.
Mission safety system softwares and stable requirements are not supported for agile model.
UML diagram:-Representation of the structure of software.Mainly used by software companies.
UML -- Unified Modelling Language represent the structure of the software into many different diagrams.
UML can capture different views like user's view,Structural view,Behavioural view,Implementation and Environmental view.
UML is a graphical language for visualize, specify, constructing and documenting information about software systems.
The Customer,developer,tester,programmer or anyone who engages in the project management can understand the concept and full information about the software by seeing the UML diagrams.
It is a Blueprint of the Software and the different UML diagrams are used for different purposes.
UML diagrams:-
1)Use Case Diagram
2)State chart Representation
3)Activity Diagram
4)Interaction Diagrams
5)Sequence Diagrams
6)Colloboration Diagram
7)Deployment diagram
8)Component Diagram
9)ER diagram
10)Class Diagram
11)Communication diagram
12)Data flow diagram
13)Flow chart
14)Profile diagram
15) object diagram.
Above diagrams are grouped into 2 main Categories:-
Behavioral UML Diagram
Structural UML Diagram
What is your impression of Agile as a process, and UML as a documentation system?
How does DevOps support the agile system development process?
1. Mary is a key stakeholder in your company and is part of your Agile project. She is at a planning meeting and says, “I thought you don’t do formal planning in Agile.” You respond: Select one: a. We plan project, but we keep the focus on immediate items and we value working software over comprehensive documentation b. We plan as other projects do and incorporate stakeholder considerations into the planning to produce working software at the end c. Normally...
How Agile can be used for the bottom-up planning process (what steps) and the rationales (why) of identifying and selecting Information System (IS) development project.
What is the single most important positive element of the Agile Process Approach that could be applied to traditional manufacturing companies and/or to large software development projects?
True/ False a. The main reason behind the drive to develop and adopt agile development methodologies is the desire to cope with frequent and unexpected changes in requirements, team status, and environmental conditions b. The main justification for introducing the so called agile technologies stems from the fact that ... Traditional processes such as waterfall are not very cost effective. All big software companies are already using such technologies. The development process should be reilient to the fact...
User documentation _____. allows users to prepare overall documentation, such as process descriptions and report layouts, early in the software development life cycle (SDLC) describes a system’s functions and how they are implemented contains all the information needed for users to process and distribute online and printed output consists of instructions and information to users who will interact with the system
Does agile development work for every project? In your opinion, why might agile development not be suitable for companies all the time? What are some notable reasons why agile would not be the most effective or efficient methodology?
Your company has recently implemented an agile portfolio management process. You are the portfolio manager and are constantly getting complaints about the number of projects that are postponed at each quarterly review only to be restarted at the next quarterly review. How do you respond?
If a traditional manufacturing company attempts to execute a product development process similar to the Agile Process Approach what would be the biggest risks associated with using the process. How, if at all, could these risks be minimized?