Submitted by: Tawfin Rahman

ID: 2311520030

Submitted to: Prof. Dr. M. Mesbahuddin Sarker

MIS107
LECTURE 14
Building
Information
Systems
 Prototyping
Rapid prototyping lets users test ideas early with cheap, quick models. This feedback helps refine the design
before building the final system. It's like sketching before painting - fast, messy drafts lead to a better final
product.

Prototyping in a Nutshell:
Build a bare-bones version of the system quickly and affordably.
Let users play around with it to understand their needs better.
Use their feedback to improve the design before diving into development.
 Prototyping Steps
Prototyping in Four Steps:

Identify core user needs

01

Rapid Build: Systems designer quickly creates a basic,

02 working model

03 User interacts with the prototype and provides

feedback.

03 Refining the Prototype - This cycle continues until the

user is happy

Once finalized, the prototype transitions into a working model, guiding the application's final design.
In some cases, it might even become the final product itself.
 Prototyping Advantages vs Disadvantages
Benefits:
Reduced Uncertainty: Prototyping shines when there's ambiguity in either the desired features or overall
design.
User-Centered Design: By actively involving users throughout the process, prototyping increases the likelihood
of a system that meets their needs.
Early Feedback: It allows for quick user feedback, enabling iterative improvements before significant
development takes place.

Drawbacks:
Skipped Steps: Rapid prototyping can lead to overlooking crucial development phases like comprehensive
testing or documentation.
Production Hurdles: A functional prototype might mask issues that arise when handling larger data volumes or
increased users in a real-world setting.
Management Misconceptions: A seemingly successful prototype might lead management to underestimate
the effort needed for a polished final product.
 Rapid Application Development
In a nutshell
Rapid Application Development (RAD) delivers the previous process of making functional systems quickly through:
Visual tools: Building user interfaces becomes faster with drag-and-drop components.
Iterative prototyping: Key features are built and tested repeatedly for continuous improvement.
Automated code generation: Tools can streamline coding tasks, saving time.
Collaborative teamwork: Close interaction between users and developers ensures the final product aligns
with needs.

The RAD model prioritizes rapid development through iterative prototyping.

 Rapid Application Development
RAD projects work through collaboration - developers, specialists, and customers work together
while following iterative and incremental models

RAD model organizes the analysis, design, build

and test phases into a series of short, iterative
development cycles
 RAD Model Design
Modelling Concepts/Phases overall:

1.0 Business Modeling

The business model for the product in development is structured around information flow and distribution among business
channels. A thorough business analysis identifies essential information, how it's acquired, processed, and factors driving
successful information flow.
 RAD Model Design
Modelling Concepts/Phases overall:

2.0 Data Modeling

Information collected in the Business Modeling phase undergoes review and analysis to identify essential data objects for the
business. Attributes of these data sets are identified and defined. Relationships between data objects are established and
detailed in alignment with the business model.
 RAD Model Design
Modelling Concepts/Phases overall:

4.0 Application Generation

The system is constructed, and coding is executed using automation tools to transform process and data
models into prototypes.

5.0 Testing and Turnover

In the RAD model, overall testing time is diminished because
prototypes undergo independent testing in each iteration.

However, thorough testing of data flow and component interfaces

with complete coverage is essential. With most programming
components already tested, the risk of major issues is reduced.
 RAD Model Vs Traditional SDLC
Traditional SDLC:

Follows a rigid process model.

Emphasizes requirement analysis and gathering before coding.
Pressures customers to sign off requirements before the project starts.
Lacks a working build for a long time, delaying customer feedback.
Rigid change process makes major modifications difficult after initial approval.

RAD Model:

Focuses on iterative and incremental delivery of working models.

Enables rapid delivery and continuous customer involvement.
Reduces the risk of not meeting user requirements through ongoing feedback.
 RAD Model - Pros and Cons
Pros:
Accommodates changing requirements.
Allows progress measurement.
Short iteration times with powerful RAD tools.
High productivity with fewer people.
Reduced development time.
Increased reusability of components.
Quick initial reviews.
Encourages customer feedback.
Early integration reduces issues.
Cons:
Requires a technically strong team for identifying business requirements.
Only suitable for modular systems.
Needs highly skilled developers/designers.
High dependency on modeling skills.
High cost of modeling and automated code generation.
Increased management complexity.
Best for component-based, scalable systems.
Requires constant user involvement.
Ideal for projects with shorter development times.
 Joint Application Design (JAD) Model
Joint Application Design (JAD) is a technique used to accelerate the generation of information requirements
and develop the initial systems design. It involves end users and information systems specialists in interactive
sessions to discuss the system's design.

Well-prepared and facilitated JAD sessions can

significantly speed up the design phase and
involve users intensively.
 Agile Model
The Agile SDLC model combines iterative and incremental processes, focusing on adaptability and customer
satisfaction through rapid delivery of working software. Agile breaks the product into small incremental builds,
provided in iterations lasting one to three weeks. Each iteration involves cross-functional teams working on:
Planning
Requirements Analysis
Design
Coding
Unit Testing
Acceptance Testing

At the end of each iteration, a

working product is shown to the
customer and key stakeholders.
 Agile Model
Popular Agile methods include Rational Unified Process (1994), Scrum (1995), Crystal Clear, Extreme
Programming (1996), Adaptive Software Development, Feature Driven Development, and Dynamic
Systems Development Method (DSDM) (1995). Collectively, these are known as Agile Methodologies,
following the Agile Manifesto published in 2001.

Agile Manifesto Principles:

Individuals and interactions: Emphasizes self-organization, motivation, and

collaboration through co-location and pair programming.
Working software: Demonstrating working software is the best way to communicate
with customers and understand their requirements, rather than relying solely on
documentation.
Customer collaboration: Continuous customer interaction is crucial, as initial
requirements may not be fully gathered at the project's start.
Responding to change: Focuses on quick responses to change and continuous
development.
 Agile Vs Traditional SDLC Models
Agile:
Based on adaptive software development methods.
Uses an adaptive approach with no detailed upfront planning.
Future tasks are determined by the features that need to be
developed.
Emphasizes feature-driven development and dynamic
adaptation to changing requirements.
Frequent testing through release iterations minimizes the risk of
major failures.
Customer interaction and open communication with minimal
documentation are key.
Teams work closely, often in the same location.
Traditional SDLC (e.g., Waterfall):
Based on a predictive approach.
Involves detailed planning with a complete forecast of tasks
and features for the next few months or the entire product
life cycle.
Relies on initial requirement analysis and planning.
Changes go through strict change control management and
prioritization.
 Agile Model - Pro’s and Con’s
Pros:
Realistic approach to software development.
Promotes teamwork and cross-training.
Rapid development and demonstration of functionality.
Minimal resource requirements.
Suitable for fixed or changing requirements.
Early delivery of partial working solutions.
Ideal for environments with steady change.
Minimal rules and easy documentation.
Supports concurrent development and delivery.
Little to no planning needed.
Easy to manage.
Provides flexibility to developers.
Cons:
Not suitable for complex dependencies.
Higher risk for sustainability, maintainability, and extensibility
issues.
Requires an overall plan, an agile leader, and agile PM
practices.
Strict delivery management dictates scope and deadlines.
Heavy reliance on customer interaction; unclear customer
input can mislead the team.
High individual dependency due to minimal documentation.
Challenging technology transfer to new team members
because of lack of documentation.
 Mobile Application Development (MAD)
Developing mobile applications differs significantly from PC development due to smaller screens. Mobile apps
favor finger and multi-touch gestures over keyboards. They need to be optimized for specific tasks, designed
for usability, and should not try to do too much.

The user experience on mobile is fundamentally different from desktops or laptops. Prioritizing resource
savings—bandwidth, screen space, memory, processing, data entry, and user gestures—is crucial.
 Outsourcing
Outsourcing may be domestic or international.

Domestic outsourcing occurs when firms lack specific skills or

resources.

Offshore outsourcing is cost-driven, facilitated by technology

and the internet. It offers cost savings and technology assets
and skills.

Pros:
No need to hire more employees, saving money on benefits and training.
Access to a larger talent pool worldwide, offering specialized help.
Lower labor costs while maintaining quality by tapping into a global talent pool

Cons:
Lack of control as you give up some authority when hiring contractors.
Communication issues due to differences in time zones and preferred methods.
Potential problems with quality if expectations aren't communicated clearly upfront.
 Outsourcing - Impact on Company
Culture
Impact of Outsourcing on Company Culture:
Upsets employees who feel replaced.
Confuses employees about the reasons for outsourcing specific tasks.
Adds challenges to the daily workflow of the company.
May lead to decreased morale and productivity if not handled carefully.
Requires clear communication and transparency to mitigate potential negative effects.
Can strain relationships between management and employees if not discussed openly.
END OF LECTURE 14