Mapa mental
REQUIREMENTS MODELING
Conteúdo do mapa
REQUIREMENTS MODELING
JAD
- Definition
- It involves continuous interacting with the users and designers of the system in development.
- Methodology system originally used for designing a computer-based system, but can be applied to any development process.
- During JAD session, activities such as open discussion above system requirement, documentation and prototyping are being done
- JAD produces requirements model
- JAD team
- JAD team organizes meetings with the objective to get accurate system requirement from the participants.
- System analyst will collect data through discussion, asking question, taking notes and provide support to the team.
- JAD Roles
- JAD Project Leader
- Develops agenda
- Acts as facilitator
- Lead as JAD session
- Top Management
- Provides enterprise-level authorization & support for the project
- Manager
- Project support to the project at department level
- Understand how the project support business function and requirements
- System Analyst
- Provide technical assistance & resources (security,backup, hardware)
- User
- Provide overall requirement of the system (input, output)
- JAD Project Leader
- Advantages & Disadvantages
- Definition
RAD
- Definition
- Method of software development which heavily emphasizes rapid prototyping iterative delivery.
- Created By
- Introduced in 1991 in James Martin's book by the same name.
- Method
- Agile development method
- Radical steps : Generally follow cyclical process
- 1. planning requirements
- 2. User design
- 3. Rapid construction
- 4. Cutover
- Model Design
- Most Crucial When Considering RAD Is The Right
- Measurable Progress
- Quickly generate productive code
- Compartmentalization of system compenent
- Rapid, constant user feedback
- Early system integration
- Simple adaptability
- Advantages
- It inherent synergy with the requirements of the medium itself software
- Definition
AGILE (Fastest Method)
- Advantages
- Very flexible & efficient in dealing with change
- Frequent deliverable constantly validate the project
- Reduce risk
- Develop System
- Incrementally by build series of prototypes & adjusting them to users requirement regularly
- Earlier Vision
- Develop revise
- Extend
- Final Product
- Merge
- Emphasize
- Continuous feedback
- Incremental step
- Prior step
- Incremental step
- Continuous feedback
- Disadvantages
- Team members higher level of technical & interpersonal skills
- Lack of structure & documentation can introduce risk factor
- Subject to significant change in scope
- Scrum Framework
- Advantages
MODELING TOOLS & TECHNIQUES
- Business Process Modeling (BPM)
- Represents one or more business process.
- Include shape & symbols
- Use standard language
- Business process diagram
- Represents one or more business process.
- Data Flow Diagram (DFD)
- System stores, processes & transform data
- The process
- Use Case Diagrams
- Represent the interaction between users and the system
- Validation process of credit card
- Users : customer
- Process : valid / invalid
- 1. Enter the credit card number & expiration date
- 2. Verifies card
- If valid = verify
- If invalid = system reject
- 3. TAC code
- If valid = Receive message (code)
- If invalid = no message
- Precondition
- Customer must select only 1 item
- Post condition
- Info has valid then customer can proceed with order
- Assumption : none
- Sequence Diagram
- Business Process Modeling (BPM)
FACT FINDING
- Interviews
- Questionnaires
- Document Review
- Observation
- Brainstorming
Imagens e arquivos do mapa
Informações
- Descrição
- Mapa Mental sobre REQUIREMENTS MODELING, criado por ain. habib em 01-10-2019.
- Criado por
- ain. habib · out 2019
- Atualizado
- 1 out 2019
- Visualizações
- 23
- Avaliação
