Friday, July 28, 2017

Overview system analysis/design concepts [Mod -1] [TSLC-] For System Analysis & Design

1. Understand Data processing system:

A data processing system takes raw data and, through the power of computer automation, produces information that a set of program applications has validated. Information includes text, arithmetic calculations, formulas and various other types of information and data based on the computer system. A data processing system is also called an automated data processing (ADP) unit or an electronic data processing (EDP) unit.

2. Explain Management Information System:

A management information system (MIS) is a set of systems and procedures that gather information from a range of sources, compile it and present it in a readable format. Managers use an MIS to create reports that provide them with a comprehensive overview of all the information they need to make decisions ranging from daily minutiae to top-level strategy. Today's management information systems rely largely on technology to compile and present data, but the concept is older than modern computing technologies.
The main purpose of a management information system is to make managers' decision-making more efficient and productive. By pooling information from a range of sources into a single database and presenting the information in a logical format, an MIS can provide managers with everything they need to make highly informed decisions and perform in-depth analysis of operational issues.

An MIS can collect nearly any type of information managers require. They can view financial data such as daily revenues and expenses at a glance and attribute them to specific departments or groups.

3. Describe Data support system:

A data support system (DSS) is a computer program application that analyzes business data and presents it so that users can make business decisions more easily. It is an "informational application" (to distinguish it from an "operational application" that collects the data in the course of normal business operation).Typical information that a decision support application might gather and present would be:
  • Comparative sales figures between one week and the next.
  • Projected revenue figures based on new product sales assumptions.
  • The consequences of different decision alternatives, given past experience in a context that is described.

A data support system may present information graphically and may include an expert system or artificial intelligence (AI). It may be aimed at business executives or some other group of knowledge workers.

4. Understand artificial intelligence:

Artificial intelligence is a branch of computer science that aims to create intelligent machines. It has become an essential part of the technology industry.

Research associated with artificial intelligence is highly technical and specialized. The core problems of artificial intelligence include programming computers for certain traits such as:

  •     Knowledge
  •     Reasoning
  •     Problem solving
  •     Perception
  •     Learning
  •     Planning
  •     Ability to manipulate and move objects

Robotics is also a major field related to AI. Robots require intelligence to handle tasks such as object manipulation and navigation, along with sub-problems of localization, motion planning and mapping.

Goals of AI:

    To Create Expert Systems − The systems which exhibit intelligent behavior, learn, demonstrate, explain, and advice its users.

    To Implement Human Intelligence in Machines − Creating systems that understand, think, learn, and behave like humans.



5. Identify system analysis and 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


6. Familiarize with system development and flow:

An effective System Development Life Cycle (SDLC) should result in a high quality system that meets customer expectations, reaches completion within time and cost evaluations, and works effectively and efficiently in the current and planned Information Technology infrastructure.

System Development Life Cycle (SDLC) is a conceptual model which includes policies and procedures for developing or altering systems throughout their life cycles.

SDLC is used by analysts to develop an information system. SDLC includes the following activities −
  1. Feasibility Study or Planning:
    Define the problem and scope of existing system.

    Overview the new system and determine its objectives.

    Confirm project feasibility and produce the project Schedule.

    During this phase, threats, constraints, integration and security of system are also considered.

    A feasibility report for the entire project is created at the end of this phase.


   
2. Analysis and Specification

    Gather, analyze, and validate the information.

    Define the requirements and prototypes for new system.

    Evaluate the alternatives and prioritize the requirements.

    Examine the information needs of end-user and enhances the system goal.

    A Software Requirement Specification (SRS) document, which specifies the software, hardware, functional, and network requirements of the system is prepared at the end of this phase.

3. System Design

    Includes the design of application, network, databases, user interfaces, and system interfaces.

    Transform the SRS document into logical structure, which contains detailed and complete set of specifications that can be implemented in a programming language.

    Create a contingency, training, maintenance, and operation plan.

    Review the proposed design. Ensure that the final design must meet the requirements stated in SRS document.

    Finally, prepare a design document which will be used during next phases.

4. Implementation

    Implement the design into source code through coding.

    Combine all the modules together into training environment that detects errors and defects.

    A test report which contains errors is prepared through test plan that includes test related tasks such as test case generation, testing criteria, and resource allocation for testing.

    Integrate the information system into its environment and install the new system.

5. Maintenance/Support

    Include all the activities such as phone support or physical on-site support for users that is required once the system is installing.

    Implement the changes that software might undergo over a period of time, or implement any new requirements after the software is deployed at the customer location.

    It also includes handling the residual errors and resolve any issues that may exist in the system even after the testing phase.

    Maintenance and support may be needed for a longer time for large systems and for a short time for smaller systems.

7. Prepare major system development models:

The Software Development Life Cycle is a process that ensures good software is built. Those development life cycle are based on different models as per their best requirement. Which can achieve high goal with less effort and much less time. Here are list of some more specific on SDLC (System Development Life Cycle):

  1. Rapid Application Development
  2. Test-Driven Development     
  3. Waterfall Model
  4. Iterative Model 
  5. Extreme Programming
  6. Scaled Agile Framework
  7. Agile Model     
  8. Scrum     
  9. Rational Unified Process
  10. Big Bang Model     
  11. V-Model     
  12. Conceptual Model
  13. Kaizen Model     
  14. Kanban Model     
  15. Spiral Model
Among all of these we are going to read about these two:
♦ Water fall model
♦ Spiral model

1. Water Fall Model:
The Waterfall Model was the first Process Model to be introduced.
It is very simple to understand and use. In a waterfall model, each phase must be completed before the next phase can begin and there is no overlapping in the phases.
The Waterfall model is the earliest SDLC approach that was used for software development.
The waterfall Model illustrates the software development process in a linear sequential flow. This means that any phase in the development process begins only if the previous phase is complete. In this waterfall model, the phases do not overlap.

Waterfall Model - Design

Waterfall approach was first SDLC Model to be used widely in Software Engineering to ensure success of the project. In "The Waterfall" approach, the whole process of software development is divided into separate phases. In this Waterfall model, typically, the outcome of one phase acts as the input for the next phase sequentially.
The following illustration is a representation of the different phases of the Waterfall Model.
SDLC Waterfall Model The sequential phases in Waterfall model are −
  • Requirement Gathering and analysis − All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification document.
  • System Design − The requirement specifications from first phase are studied in this phase and the system design is prepared. This system design helps in specifying hardware and system requirements and helps in defining the overall system architecture.
  • Implementation − With inputs from the system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality, which is referred to as Unit Testing.
  • Integration and Testing − All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.
  • Deployment of system − Once the functional and non-functional testing is done; the product is deployed in the customer environment or released into the market.
  • Maintenance − There are some issues which come up in the client environment. To fix those issues, patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.
All these phases are cascaded to each other in which progress is seen as flowing steadily downwards (like a waterfall) through the phases. The next phase is started only after the defined set of goals are achieved for previous phase and it is signed off, so the name "Waterfall Model". In this model, phases do not overlap.
The spiral model combines the idea of iterative development with the systematic, controlled aspects of the waterfall model. This Spiral model is a combination of iterative development process model and sequential linear development model i.e. the waterfall model with a very high emphasis on risk analysis. It allows incremental releases of the product or incremental refinement through each iteration around the spiral.

2. Spiral Model - Design

The spiral model has four phases. A software project repeatedly passes through these phases in iterations called Spirals.

Identification

This phase starts with gathering the business requirements in the baseline spiral. In the subsequent spirals as the product matures, identification of system requirements, subsystem requirements and unit requirements are all done in this phase.
This phase also includes understanding the system requirements by continuous communication between the customer and the system analyst. At the end of the spiral, the product is deployed in the identified market.

Design

The Design phase starts with the conceptual design in the baseline spiral and involves architectural design, logical design of modules, physical product design and the final design in the subsequent spirals.

Construct or Build

The Construct phase refers to production of the actual software product at every spiral. In the baseline spiral, when the product is just thought of and the design is being developed a POC (Proof of Concept) is developed in this phase to get customer feedback.
Then in the subsequent spirals with higher clarity on requirements and design details a working model of the software called build is produced with a version number. These builds are sent to the customer for feedback.

Evaluation and Risk Analysis

Risk Analysis includes identifying, estimating and monitoring the technical feasibility and management risks, such as schedule slippage and cost overrun. After testing the build, at the end of first iteration, the customer evaluates the software and provides feedback.
The following illustration is a representation of the Spiral Model, listing the activities in each phase.
SDLC Spiral Model Based on the customer evaluation, the software development process enters the next iteration and subsequently follows the linear approach to implement the feedback suggested by the customer. The process of iterations along the spiral continues throughout the life of the software.


No comments:

Post a Comment