Software development and processes – RAD:

 The Rapid Application Development Model was first proposed by IBM in the 1980s.
The RAD model is a type of incremental process model in which there is extremely
short development cycle.
 When the requirements are fully understood and the component-based construction
approach is adopted then the RAD model is used.
 Various phases in RAD are Requirements Gathering, Analysis and Planning, Design,
Build or Construction, and finally Deployment .
 Multiple teams work on developing the software system using RAD model parallelly.

This model consists of 4 basic phases:

Requirements Planning: It involves the use of various techniques used in requirements
elicitation like brainstorming, task analysis, form analysis, user scenarios, FAST (Facilitated
Application Development Technique), etc. It also consists of the entire structured plan
describing the critical data, methods to obtain it, and then processing it to form a final refined
model.
User Description: This phase consists of taking user feedback and building the prototype
using developer tools. In other words, it includes re-examination and validation of the data
collected in the first phase. The dataset attributes are also identified and elucidated in this
phase.
Construction: In this phase, refinement of the prototype and delivery takes place. It includes
the actual use of powerful automated tools to transform processes and data models into the
final working product. All the required modifications and enhancements are too done in this
phase.
Cutover: All the interfaces between the independent modules developed by separate teams
have to be tested properly. The use of powerfully automated tools and subparts makes testing
easier. This is followed by acceptance testing by the user.
When to use RAD Model?
 When the customer has well-known requirements, the user is involved throughout the
life cycle, the project can be time-boxed, the functionality delivered in increments, high
performance is not required, low technical risks are involved and the system can be
modularized.
 In these cases, we can use the RAD Model. when it is necessary to design a system that
can be divided into smaller units within two to three months.
 when there is enough money in the budget to pay for both the expense of automated
tools for code creation and designers for modeling

Advantages:

 The use of reusable components helps to reduce the cycle time of the project.
 Feedback from the customer is available at the initial stages.
 Reduced costs as fewer developers are required.
 The use of powerful development tools results in better quality products in
comparatively shorter time spans.
 The progress and development of the project can be measured through the
various stages.
Disadvantages:

 The use of powerful and efficient tools requires highly skilled

professionals.
 The absence of reusable components can lead to the failure of the
project.
 The team leader must work closely with the developers and customers
to close the project on time.
 The systems which cannot be modularized suitably cannot use this
model.
 Customer involvement is required throughout the life cycle
Applications:

 This model should be used for a system with known requirements and requiring a short
development time.
 It is also suitable for projects where requirements can be modularized and reusable
components are also available for development.
 The model can also be used when already existing system components can be used in
developing a new system with minimum changes.

RUP : stands for Rational Unified Process, which is a software development methodology
created by Rational Software, later acquired by IBM. It's an iterative and incremental approach
to software development that focuses on flexibility, adaptability, and producing high-quality
software.
RUP provides a framework for software development that is guided by four phases:
Inception: In this phase, the project scope, feasibility, and initial planning are established. The
main goal is to define the project's purpose and scope.
Elaboration: This phase involves further refinement of the project requirements, architecture,
and design. Risks are identified and mitigated, and a solid foundation for the project is
established.
Construction: During this phase, the actual development of the software occurs. The emphasis
is on coding, testing, and integration to build the product.
Transition: In this phase, the software is deployed to users. User feedback is collected, and
any necessary adjustments or improvements are made.
Advantages:
 RUP emphasizes the importance of iterative development, continuous integration, and
frequent feedback from stakeholders throughout the software development life cycle.
 It uses various artifacts, such as models, diagrams, and documents, to describe the
software being developed
 The methodology is adaptable and can be tailored to specific project needs, allowing
teams to adjust and adopt practices based on the project's size, complexity, and
requirements.
Agile Software Development:
 Agile is a methodology or approach to software development that prioritizes flexibility,
collaboration, adaptability, and customer satisfaction.
 It emphasizes iterative development, continuous feedback, and the ability to respond to
change quickly throughout the software development life cycle.

Key principle of Agile Software Development:

Iterative Development:
 Breaking down the development process into smaller, manageable increments called
iterations or sprints.
 Each iteration results in a potentially shippable product increment.
Collaboration and Customer Involvement: Encouraging close collaboration between cross-
functional teams, including developers, testers, and business stakeholders, as well as involving
customers or end-users throughout the development process to ensure the product meets their
needs.
 Agile methodologies include various frameworks and approaches, such as Scrum,
Kanban, Extreme Programming (XP), Lean, and more.
 Each framework has its own set of practices, ceremonies, and roles, but they all share
the common values and principles of the Agile Manifesto.
Adaptability and Flexibility: Embracing change as a natural part of the development process
and being flexible enough to accommodate changes in requirements even in later stages of
development.
Continuous Improvement: Regularly reflecting on the process and seeking ways to improve
efficiency, quality, and teamwork through retrospectives and feedback loops.
Examples of agile software:
 Scrum is a popular Agile framework that organizes work into fixed-length iterations
called sprints, with specific roles (Scrum Master, Product Owner, Development Team)
and ceremonies (Sprint Planning, Daily Stand-ups, Sprint Review, Sprint
Retrospective).
 Kanban focuses on visualizing work on a board, limiting work in progress, and
continuously improving the flow of work.
Prototyping Development phases of Software in relation to Processes:
 Prototyping can be integrated into various software development processes or
methodologies across their respective phases.
 Here's an overview of how prototyping aligns with different phases in software
development processes:

Waterfall Model:
Requirements Gathering:
 In the Waterfall model, prototyping may be used to create a basic model to help users
better understand their requirements and provide feedback.
 It assists in refining initial requirements before finalizing them.
Design:
 Prototyping can generate mock-ups or models to showcase the software's expected
appearance and interactions.
 It aids in designing the user interface and understanding usability requirements.
Implementation:
 Prototyping may be limited in the Waterfall model's implementation phase, as the focus
is on following the design and specifications strictly.
 Prototypes might inform the development process to a certain extent but may not be
directly integrated into the final product.
Testing:
 Limited prototyping in the Waterfall model may have already occurred in earlier stages.
 Testing primarily focuses on the final product based on the specifications outlined in
the preceding phases.
 Agile Methodologies (e.g., Scrum):

Iteration Planning:
 Prototyping is often used during sprint planning to outline what functionalities will be
developed.
 Initial prototypes may aid in understanding and scoping user stories.

Development:

 Agile allows continuous development and iteration.

 Prototyping is prevalent in this phase, where multiple iterations are created, tested, and
refined based on feedback.

Review and Feedback:

 At the end of each sprint or iteration, prototypes are demonstrated to stakeholders for
feedback.
 This feedback loop helps refine the product incrementally.
Adaptation and Iteration:
Based on feedback received in each iteration, prototypes are refined and adjusted. The
continuous nature of Agile allows for flexibility and the incorporation of changes
throughout the development process.

Rapid Application Development (RAD):

Prototyping:
 RAD methodologies heavily emphasize prototyping throughout the entire software
development life cycle.
 Prototyping in RAD is not just limited to specific phases but is a continuous process to
rapidly develop and refine the software.

User Feedback and Iteration:

RAD involves multiple iterations of prototyping, where user feedback guides each
iteration, resulting in a more refined and user-centric final product.
Comparison
 The extent and integration of prototyping can vary based on the software development
methodology, it's most commonly associated with Agile methodologies and RAD due
to their iterative and user-centric nature.
 Prototyping in these methodologies is pervasive, allowing for continuous improvement
and user involvement throughout the development process.

What to develop? – Requirements gathering and Analysis:

Requirements gathering and analysis is a crucial phase in software development. It

involves understanding and documenting what needs to be developed, ensuring that the
 software will meet the needs of its users, stakeholders, and the business. Here's a
breakdown of activities and key considerations during this phase:

Activities in Requirements Gathering and Analysis:

Stakeholder Identification:

 Identify and involve all stakeholders who will be affected by or have a say in the
software being developed.
 This includes end-users, clients, managers, and other relevant parties.

Elicitation of Requirements:

 Use various techniques such as interviews, surveys, workshops, and observations to

gather information about the needs and expectations of stakeholders.
 Capture functional and non-functional requirements.

Documentation:
 Document gathered requirements in a clear, concise, and unambiguous manner.
 Use different formats like use cases, user stories, requirement documents, diagrams, or
prototypes to represent requirements.

Analysis and Prioritization:

 Analyse gathered requirements to ensure they are consistent, complete, and feasible.
 Prioritize requirements based on their importance, impact, and dependencies.

Validation and Verification:

 Validate requirements with stakeholders to ensure they accurately reflect their needs.
 Verify that the requirements are understandable, achievable, and aligned with the
project goals.

Traceability:

 Establish traceability between requirements and other project artifacts (design, test
cases, etc.).
 This helps ensure that every requirement has proper coverage and is addressed during
development.
Key Considerations

Clarity and Precision:

 Ensure that requirements are clear, specific, and unambiguous to avoid

misinterpretation during development.
 Prioritization and Trade-offs:

 Prioritize requirements based on their importance to stakeholders and the project's

goals.
 Understand trade-offs between conflicting requirements.

Involvement of Stakeholders:

 Engage stakeholders throughout the process to gather accurate and comprehensive

requirements.
 Regular feedback ensures alignment with their needs.

Validation and Verification:

 Rigorously validate requirements to prevent misunderstandings and verify that they

align with business objectives.

Flexibility and Adaptability:

 Be prepared for changes as requirements may evolve during the development process.
 Have mechanisms in place to manage changes efficiently.

Documentation and Communication:

 Document requirements comprehensively and communicate them effectively to all
stakeholders and development teams involved.

Types- functional, nonfunctional, system:

 Various types of requirements are gathered to define the characteristics, features, and
constraints of the software being developed.
 These requirements are typically categorized into different types based on their nature
and characteristics. Here are the primary types of requirements:

Functional Requirements:
 Functional requirements describe the specific functionalities or capabilities that the
software system must possess.
 They outline what the system should do and how it should perform under specific
conditions.
Examples:
 User authentication and login functionality
 Calculation of payroll for employees
 Generation of reports based on user queries
 Sending automated email notifications
Non-functional Requirements:
 Non-functional requirements define the qualities or attributes that the system
should possess rather than specific functionalities.
 These requirements address aspects related to performance, usability, security,
reliability, scalability, and more.

Examples:

Performance: Response time for system operations should be less than 2

seconds.
 Security: User data should be encrypted and stored securely.
 Usability: The user interface should be intuitive and accessible.
 Reliability: The system should be available 99.9% of the time.
System Requirements:
 System requirements encompass both functional and non-functional
requirements but at a broader level.
 They describe the overall behaviour, attributes, and constraints of the entire
software system, including interfaces with external systems, hardware
requirements, and more.
Examples:

 Compatibility: The software should be compatible with specific operating

systems (Windows, macOS, Linux).
 Interfaces: The system should integrate with external APIs for payment
processing.
Hardware Requirements:
Minimum RAM, processor speed, and storage requirements for the software to run
efficiently.

User Interface:
 Refers to the means through which users interact with a computer system or software
application.
 It encompasses everything a user interacts with, including screens, pages, buttons,
icons, text, graphics, and any other elements users interact with to use a software
product.
Components of User Interface (UI):

Graphical User Interface (GUI):

 GUI refers to the visual elements of the interface, such as windows, icons, buttons,
menus, and other graphical elements that users can interact with using a mouse,
keyboard, or touch.
Navigation Design:

 This aspect focuses on how users move through the software.

 It involves designing intuitive and efficient navigation paths, menus, breadcrumbs,
and links to help users easily access different parts of the application.
Layout and Information Architecture:

 Designing the layout involves organizing and presenting information in a structured

and understandable manner.
 It includes the placement of elements, grouping related information, and organizing
content hierarchically.

Input Controls:

 Input controls encompass various elements that allow users to input data or interact
with the software, such as text fields, checkboxes, radio buttons, dropdown lists,
sliders, and date pickers.

Feedback and Response:

 Providing feedback to users based on their interactions is essential for a good UI.
Visual cues, messages, and system responses help users understand the outcome of
their actions.

Visual Design and Branding:

 Visual design involves the aesthetic aspects of the UI, including color schemes,
typography, iconography, and overall styling.
 Branding elements ensure consistency with the organization's identity.

Importance of a Good User Interface:

 Enhanced User Experience (UX): A well-designed UI contributes to a positive user

experience by making the software intuitive, efficient, and user-friendly.

 Increased Productivity: Intuitive interfaces reduce the learning curve for users and
enable them to perform tasks more efficiently, ultimately improving productivity.

 Reduced Errors: Clear and consistent UI design can help minimize user errors by
providing cues and guidance, preventing misunderstandings.

 Higher Adoption Rates: Intuitive and visually appealing interfaces often lead to
higher user acceptance and adoption rates.

UI Design Process:
 Research and Analysis: Understand user needs, preferences, and behaviors.

 Wireframing and Prototyping: Create visual representations and interactive

prototypes to visualize the layout and functionality.

 Visual Design: Apply color schemes, typography, and branding elements to enhance
aesthetics.
  Usability Testing: Test the UI with real users to gather feedback and make iterative
improvements.

Implementation and Development: Integrate the UI design into the software application.

Quality requirements and putting together– UML use cases, scenarios

 Quality requirements are crucial aspects of software development that focus on
defining the expected quality attributes and characteristics of a system.
 These requirements help ensure that the software meets user expectations and
functions effectively.
 When putting together UML (Unified Modeling Language) use cases and scenarios,
quality requirements play a significant role in shaping the system's functionality and
behavior.

Here's how quality requirements can be integrated into UML use cases and scenarios:

Identify Quality Attributes:

 Start by identifying the quality attributes relevant to the system.
 These can include performance, security, usability, reliability, scalability,
maintainability, etc. Each of these attributes will influence the design and
implementation of the system.

Quality Requirement Artifacts:

 Create specific artifacts or documentation to capture quality requirements. Use cases
and scenarios can be annotated or extended to include information about quality
attributes.
 For instance, you might add notes or annotations to use case diagrams or scenarios to
highlight particular quality requirements associated with each use case.

Traceability and Prioritization:

 Establish traceability between use cases, scenarios, and quality requirements. This
ensures that each functional requirement (use case) is aligned with the corresponding
quality attributes.
 Prioritize these requirements based on their significance and impact on the system.

Use Case Descriptions and Quality Considerations:

 Within the detailed descriptions of each use case, elaborate on how quality attributes
relate to that specific functionality.
 For instance, if a use case deals with authentication, discuss how security
requirements like encryption, access control, etc., are incorporated.

Scenarios and Quality Checks:

 When describing scenarios (sequence of steps) within use cases, consider including
quality checks or conditions at each step.
 For example, within a scenario related to user login, specify checks for secure
password handling or authentication procedures.
  Integrating quality requirements into UML use cases and scenarios ensures that the
developed software meets the desired quality standards while addressing the
functional aspects specified by users or stakeholders.

Validation and Verification:

 During the validation and verification phases, use quality requirements as a
benchmark to test the system.
 Each use case scenario can be tested against the defined quality attributes to ensure
compliance and functionality.

Iteration and Refinement:

 Quality requirements should evolve alongside use case development.
 Regularly revisit and refine quality requirements as the project progresses, ensuring
they stay aligned with the evolving system design and user needs.