Please enable JavaScript.
Coggle requires JavaScript to display documents.
System Analysis and Design, Group 7 members, Explaination, Explaination,…
System Analysis and Design
Types of information systems
Operation level
Transaction Processing System(TPS)
Employee Record keeping
Payroll Processing
Material Movement control
Order Processing
interact with external environment for the
day-to-day operations of business
Knowledge level
Office Automation System(OAS)
support
data workers
to analyze information collected then manipulate data into certain ways for sharing
Word processing
Communication via e-mail or voice mail
Electronic filing
Knowledge Work System(KWS)
support
professional workers
to create new knowledge and contribute it to organization or society
Computer-aided design(CAD) systems
Virtual Reality
Financial workstations
Higher level
Decision Support System(DSS)
search engine
consultation system
Gps route planing
support of
decision making
in all its phases but
final decision still left up to decision maker
Expert System(ES)
DENDRAL
PXDES
MYCIN
Aid of
computer program or artificial intelligence
to find the best solution for specific problem
Management Information System(MIS)
profit margin by sales region
Marketing
Daily sales report
support
management function of organization
that aid in decision making by interpreting the data
Strategic level
Group Decision Support System(GDSS)
Microsoft Exchange
Net Document Enterprise
Lotus Notes
Aid in
group collaboration permittiong group members with elecronic support
such as polling , questionnaires
Computer-Supported Collaborative Work System(CSCWS)
Video conferencing
Web survey system
support
management function of organization
that aid in decision making by interpreting the data
Executive Support System(ESS)
status access
marketing report
drill-down analysis
Help
executives to make decisions
with supporting documents or technologies
Alternative to Traditional SDLC Methodologies
Rapid Application Development (RAD)
Methodology
Decrease design and implementation time
Goal
Get some portion of system developed quickly and in the users’ hands
Focus on
Rapid delivery
Continuous integration
Reuse of the existing prototypes (components)
Gathering customer requirements through workshops or focus groups
Early testing of the prototypes by the customer using iterative concept
Approaches
Iterative development
System Prototyping
Throw-away prototyping
Prototyping
A working model of software with some limited functionality.
Benefits
Allow the users evaluate developer proposals and try them out before implementation.
Helps understand the requirements which are user specific and may not have been considered by the developer during product design.
Types
Throwaway/Rapid Prototyping
Evolutionary Prototyping
Incremental Prototyping
Extreme Prototyping
Steps
Refine objective
Identify data to be used
Plan prototype
Develop prototype
Review for feasibility
Access impact of prototype
Update documentation
Joint Application Design (JAD)
Participants
Analyst
Managers
User
Benefits
Enhances quality
Promotes team work
Accelerates design
Lowers with customer maintenance and development cost
Requires
Facilitator
Ensuring that the group sticks to the agenda
Help the group to understand key terms, jargons, and system analysis process
Sets meeting agenda
and guides discussion
Recording group's inputs, structuring information
Helping group recognize key issues and solutions
Leads a group of users
Agile methods
Motivated by recognition of software development as fluid, unpredictable, and dynamic
Key principles
Emphasize people rather than roles
Self-adaptive processes
Adaptive rather than predictive
When to use
Responsible and motivated developers
Customers who understand the process and will get involved
Unpredictable or dynamic requirements
Advantages
Satisfaction by rapid & continuous delivery of useful software
Working software is delivered frequently
Regular adaptation to changing circumstances
Disadvantages
Difficult to assess & effort required at the beginning of SDLC
Lack on necessary designing and documentation
Easily get taken off track and out of outcome
Computer-Aided Software Engineering (CASE)
Productivity tools created explicitly to improve systems analysts' routine work through the use of automated support.
Reasons for using
Increasing Analyst Productivity
Improving Analyst-User Communication
Integrating Life Cycle Activities
Accurately Assessing Maintenance Changes
Classifications
Upper CASE tools
Lower CASE tools
Integrated CASE tools
A central repository provides integrated storage of diagrams, reports, and project management specifications.
Definition
A highly organizational approaches to develop and maintain the information system.
Understand the business need
Designing and building the system
Introduce the system to the users
7 Phases of Software Development Life Cycle (SDLC)
Designing the recommended system
Activity
Design effective input
Devises the human-computer interface
Design procedures
Output
Model of actual system
Developing and documenting software
Activity
Uses structure charts and pseudocode to communicate to the programme
Output
Computer programs and system documentation
Analyzing system needs
Activity
Data dictionary
Structured decisions methods
Data flow diagrams
System proposal
Output
Solution is based on analyst qualities and professional training and interaction with users
Testing and maintaining system
Activity
Testing done by both programmers and analyst
Maintenance started routinely through life of system
Testing take place first with sample data and then actual data
Updates may be performed via vendor site on Web
Output
Updated programs
Documentation
Problems, if any
Determining human information requirements
Activity
Sampling and investing hard data
Observe decision maker's behavior and environment
Interviewing
Prototyping
Learn 5W1H of the current system
Output
Understanding on how to accomplish
work using computer
Understanding on how to make new
system more useful and usable
Implementing and evaluating system
Activity
System conversion - converting files from old to new, build database, install equipment, bring new system to production
Training users to handle system
Evaluation takes place in in every phase
Output
Trained personnel
Installed system
Identifying prooblems,opportunities and objectives
Output
Feasibility report contain problem definition and objective summaries from which management can make decision whether proceed with the proposed project
Activity
Summarizing the knowledge obtained
Estimating the scope of project
Interviewing user management
Documenting results
Object Oriented Analysis
Technical method of analyzing and designing an application based on that system's object models
Encourages planning and development of systems that are truly independent of one another
Easy to understand
Easy troubleshooting
Flexibility through polymorphism
Reuse code by inheritance to reduce effort
Abstraction
Inheritance
Encapsulation
Polymorphism
Too complex
Not very well suited for procedural applications
Group 7 members
Wong Seng Kai (17205033/1)
Abirami A/P Nagarajan (17203434/1)
Kok Herng (17203580/1)
Explaination
Explaination
Explaination
Explaination
Explaination
Explaination
Explaination
Explaination
Explaination
Definition
Pros
Cons
Principles