SYSTEM ANALYSIS AND
DESIGN
Project work
2020
LUMBINI ACADEMIC COLLEGE
SUBMITTED BY: Surendra Timalsina
SUBMITTED TO: The Department of Humanities and Social Science
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Systems Analysis and Design: A Comprehensive Guide to SDLC, Waterfall Model, and OOAD, Assignments of System Analysis and Design
A project on System analysis and design. Introduction to SDLC, OOAD, and SAD with examples
Typology: Assignments
2020/2021
1 / 16
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Systems Analysis and Design: A Comprehensive Guide to SDLC, Waterfall Model, and OOAD and more Assignments System Analysis and Design in PDF only on Docsity!
SYSTEM ANALYSIS AND
DESIGN
Project work
LUMBINI ACADEMIC COLLEGE
SUBMITTED BY: Surendra Timalsina SUBMITTED TO: The Department of Humanities and Social Science
Table of Contents
- System Development Life Cycle (SDLC)........................................................................................................
- Waterfall Model...........................................................................................................................................
- Object Oriented Analysis and Design (OOAD)..............................................................................................
- Systems Analysis....................................................................................................................................
- Systems Design......................................................................................................................................
- What is Dataflow diagram?.......................................................................................................................
- Online Shopping System............................................................................................................................
- What is context diagram?..........................................................................................................................
- Radical Methods for Determining System Requirements..........................................................................
- Steps Involved in Feasibility Analysis.........................................................................................................
- Types of Feasibilities.................................................................................................................................. - Economic Feasibility.......................................................................................................................... - Technical Feasibility........................................................................................................................... - Operational Feasibility....................................................................................................................... - Behavioral Feasibility......................................................................................................................... - Schedule Feasibility............................................................................................................................
Stage 1: Planning and Requirement Analysis This is the first phase in the systems development process. It identifies whether or not there is the need for a new system to achieve a business’s strategic objectives. This is a preliminary plan (or a feasibility study) for a company’s business initiative to acquire the resources to build on an infrastructure to modify or improve a service. The company might be trying to meet or exceed expectations for their employees, customers and stakeholders too. The purpose of this step is to find out the scope of the problem and determine solutions. Resources, costs, time, benefits and other items should be considered at this stage. Stage 2: Defining Requirements The second phase is where businesses will work on the source of their problem or the need for a change. In the event of a problem, possible solutions are submitted and analyzed to identify the best fit for the ultimate goal(s) of the project. This is where teams consider the functional requirements of the project or solution. It is also where system analysis takes place—or analyzing the needs of the end users to ensure the new system can meet their expectations. Systems analysis is vital in determining what a business’s needs are, as well as how they can be met, who will be responsible for individual pieces of the project, and what sort of timeline should be expected. There are several tools businesses can use that are specific to the second phase. They include: CASE (Computer Aided Systems/Software Engineering) Requirements gathering Structured analysis Stage 3: Designing the Product Architecture The third phase describes, in detail, the necessary specifications, features and operations that will satisfy the functional requirements of the proposed system which will be in place. This is the step for end users to discuss and determine their specific business information needs for the proposed system. It’s during this phase that they will consider the essential components (hardware and/or software) structure (networking capabilities), processing and procedures for the system to accomplish its objectives. Stage 4: Building or Developing the Product The fourth phase is when the real work begins in particular, when a programmer, network engineer and/or database developer are brought on to do the major work on the project. This work includes using a flow chart to ensure that the process of the system is properly organized. The development phase marks the end of the initial section of the process. Additionally, this phase signifies the start of production. The development stage is also characterized by instillation and change. Focusing on training can be a huge benefit during this phase. Stage 5: Testing the Product
The fifth phase involves systems integration and system testing (of programs and procedures normally carried out by a Quality Assurance (QA) professional to determine if the proposed design meets the initial set of business goals. Testing may be repeated, specifically to check for errors, bugs and interoperability. This testing will be performed until the end user finds it acceptable. Another part of this phase is verification and validation, both of which will help ensure the program’s successful completion. Stage 6: Deployment in the Market and Maintenance Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometimes product deployment happens in stages as per the business strategy of that organization. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing). Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.
The waterfall methodology is composed of seven non-overlapping stages:
- Requirements: Potential requirements, deadlines and guidelines for the project are analyzed and placed into a functional specification. This stage handles the defining and planning of the project without mentioning specific processes.
- Analysis : The system specifications are analyzed to generate product models and business logic that will guide production. This is also when financial and technical resources are audited for feasibility.
- Design: A design specification document is created to outline technical design requirements such as programming language, hardware, data sources, architecture and services.
- Coding/Implementation: The source code is developed using the models, logic and requirements designated in the prior stages. Typically, the system is designed in smaller components, or units, before being implemented together.
- T esting: This is when quality assurance, unit, system and beta tests take place to report issues that may need to be resolved. This may cause a forced repeat of the coding stage for debugging. If the system passes the tests, the waterfall continues forward.
- Operation/Deployment: The product or application is deemed fully functional and is deployed to a live environment.
- Maintenance: Corrective, adaptive and perfective maintenance is carried out indefinitely to improve, update and enhance the final product. This could include releasing patch updates or releasing new versions.
Advantages of the waterfall model Upfront documentation and planning stages allow for large or shifting teams to remain informed and move towards a common goal. Forces structured, disciplined organization. Is simple to understand, follow and arrange tasks. Facilitates departmentalization and managerial control based on schedule or deadlines. Reinforces good coding habits to define before design and then code. Allows for early design or specification changes to be made easily. Clearly defines milestones and deadlines. Disadvantages of the waterfall model Design is not adaptive; often when a flaw is found, the entire process needs to start over. Ignores the potential to receive mid-process user or client feedback and make changes based on results. Delays testing until the end of the development life cycle. Does not consider error correction. Does not handle requests for changes, scope adjustments or updates well. Reduces efficiency by not allowing processes to overlap. No working product is available until the later stages of the life cycle. Not ideal for complex, high risk, ongoing or object-oriented projects.
Solution Breakdown Design component and service oriented systems with Select Solution Factory. Implement Select Perspective, the leading Software Reuse and Component Based Development life-cycle with Select Process Director. Use proven project and mentoring skills to help teams to adopt Component Based Development and Service based architectures. Visit our Services area to see what courses and consultancy are available. Define System analysis. Systems development is systematic process which includes phases such as planning, analysis, design, deployment, and maintenance. Here, in this tutorial, we will primarily focus on − Systems analysis Systems design
Systems Analysis
It is a process of collecting and interpreting facts, identifying the problems, and decomposition of a system into its components. System analysis is conducted for the purpose of studying a system or its parts in order to identify its objectives. It is a problem solving technique that improves the system and ensures that all the components of the system work efficiently to accomplish their purpose. Analysis specifies what the system should do.
Systems Design
It is a process of planning a new business system or replacing an existing system by defining its components or modules to satisfy the specific requirements. Before planning, you need to understand the old system thoroughly and determine how computers can best be used in order to operate efficiently. System Design focuses on how to accomplish the objective of the system. System Analysis and Design (SAD) mainly focuses on − Systems Processes Technology Process Modeling Process modeling is the analytical representation or put simply an illustration of an organization’s business processes. Modeling processes is a critical component for effective business process management. Process modeling software gives an analytical representation of 'as-is' processes in an organization and contrasts it with 'to-be' processes for making them more efficient.
Why use Process Modelling? Your first step in modeling is actually pen and paper. However, to actually run a business process, you will need to digitize that process in a way that a workflow engine can understand. Business process modeling software allow you to represent your process in a digital way that can then be transferred to a live automated process. There are many benefits to business process modeling:
- Gives everyone a clear understanding of how the process works
- Provides consistency and controls the process
- Identifies and eliminates redundancies and inefficiencies
- Sets a clear starting and ending to the process Business process modeling can also help you group similar processes together and anticipate how they should operate. The primary objective of business process modeling tools is to analyze how things are right now and simulate how should they be carried out to achieve better results.
Online Shopping System Online Shopping System Data flow diagram is often used as a preliminary step to create an overview of the Shopping System without going into great detail, which can later be elaborated.it normally consists of overall application dataflow and processes of the Shopping System process. It contains all of the user flow and their entities such all the flow of Shopping, Shopping Cart, Order, Payment, Product, Delivery, Confirm Order. All of the below diagrams have been used for the visualization of data processing and structured design of the Shopping System process and working flow.
What is context diagram? A context diagram is a graphic design that clarifies the interfaces and boundaries of the project or process at hand. It not only shows the process or project in its context, it also shows the project’s interactions with other systems and users. According to Wikipedia, a context diagram is “is the highest level view of a system. Showing a. system as a whole and its inputs and outputs from/to external factors.” Further, a context diagram “shows the interactions between a system and other actors with which the system is designed to interface. System context diagrams can be helpful in understanding the context which the system will be part of.” Here is an example of a context diagram:
Types of Feasibilities
Economic Feasibility
It is evaluating the effectiveness of candidate system by using cost/benefit analysis method. It demonstrates the net benefit from the candidate system in terms of benefits and costs to the organization. The main aim of Economic Feasibility Analysis (EFS) is to estimate the economic requirements of candidate system before investments funds are committed to proposal. It prefers the alternative which will maximize the net worth of organization by earliest and highest return of funds along with lowest level of risk involved in developing the candidate system.
Technical Feasibility
It investigates the technical feasibility of each implementation alternative. It analyzes and determines whether the solution can be supported by existing technology or not. The analyst determines whether current technical resources be upgraded or added it that fulfill the new requirements. It ensures that the candidate system provides appropriate responses to what extent it can support the technical enhancement.
Operational Feasibility
It determines whether the system is operating effectively once it is developed and implemented. It ensures that the management should support the proposed system and its working feasible in the current organizational environment. It analyzes whether the users will be affected and they accept the modified or new business methods that affect the possible system benefits.
Behavioral Feasibility
It evaluates and estimates the user attitude or behavior towards the development of new system. It helps in determining if the system requires special effort to educate, retrain, transfer,
Schedule Feasibility
It ensures that the project should be completed within given time constraint or schedule. It also verifies and validates whether the deadlines of project are reasonable or not.