Introduction To System Analysis And Design

Get Started. It's Free
or sign up with your email address
Introduction To System Analysis And Design by Mind Map: Introduction To System Analysis And Design

1. 1.3 Understand Project Management

1.1. 1.3.1 Explain project planning, scheduling, monitoring, and reporting.

1.2. 1.3.2 Explain steps in project planning.

1.3. 1.3.3 Describe work breakdown structures, task patterns, and critical path analysis.

1.4. 1.3.4 Create a work breakdown structure.

1.5. 1.3.5 Explain techniques for estimating task completion times and costs.

1.6. 1.3.6 Explain leadership and project manager.

2. 1.1 Discuss Information System.

2.1. Information Systems is an academic study of systems with a specific reference to information and the complementary networks of hardware and software that people and organizations use to collect, filter, process, create and also distribute data.

2.2. The main components of information systems are computer hardware and software, telecommunications, databases and data warehouses, human resources, and procedures.

2.3. -Pyramid Diagram of Organizational levels and information requirements. -Transaction Processing System (TPS) -Management Information System (MIS)

3. 1.2 Discuss system development approach.

3.1. 1.2.1 Explain system development method:

3.1.1. a. Structured Analysis Structured analysis is a software engineering technique that uses graphical diagrams to develop and portray system specifications that are easily understood by users. These diagrams describe the steps that need to occur and the data required to meet the design function of a particular software.

3.1.2. b. Object Oriented Analysis Object-oriented analysis is a process that groups items that interact with one another, typically by class, data or behavior, to create a model that accurately represents the intended purpose of the system as a whole.

3.1.3. c. Agile/Adaptive Method Adaptive Simpson's method, also called adaptive Simpson's rule, is a method of numerical integration proposed by G.F. ... The technique is usually much more efficient than composite Simpson's rule since it uses fewer function evaluations in places where the function is well-approximated by a cubic function.

3.2. 1.2.2 Explain System Development Life Cycle (SDLC) activities:

3.2.1. a. Planning The Project Planning Phase is the second phase in the project life cycle. It involves creating of a set of plans to help guide your team through the execution and closure phases of the project. The plans created during this phase will help you to manage time, cost, quality, change, risk and issues.

3.2.2. b. Analyze The Analysis Phase is also the part of the project where you identify the overall direction that the project will take through the creation of the project strategy documents. Gathering requirements is the main attraction of the Analysis Phase.

3.2.3. c. Design Approval to progress to the Development Phase. Goals. The purpose of the Design Phase is to transform the requirements into complete and detailed system design specifications.

3.2.4. d. Development Software development lifecycle (SDLC) is a framework that defines the steps involved in the development of software. SDLC defines the complete cycle of development i.e. all the tasks involved in gathering a requirement for the maintenance of a Product.

3.2.5. e. Testing The testing phase of the software development lifecycle (SDLC) is where you focus on investigation and discovery. There are several types of testing during the test phase, including quality assurance testing (QA), system integration testing (SIT), and user acceptance testing (UAT).

3.2.6. f. Implementation The implementation and coding phase of the software development life cycle is the third phase of the SDLC process. The first phase of the SDLC is the requirements gathering and analysis phase, which is when the project team and business managers gather the wants and needs of the customer.

3.2.7. g. Maintenance The maintenance phase involves making changes to hardware, software, and documentation to support its operational effectiveness. It includes making changes to improve a system's performance, correct problems, enhance security, or address user requirements.

3.3. 1.2.3 Describe various types of life cycle models such as:

3.3.1. a. Waterfall model The Waterfall Model was 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. Waterfall model is the earliest SDLC approach that was used for software development.

3.3.2. b. Spiral Model Spiral Model is a combination of a waterfall model and iterative model. Each phase in spiral model begins with a design goal and ends with the client reviewing the progress. The spiral model was first mentioned by Barry Boehm in his 1986 paper.

3.3.3. c. Iterative and incremental development Iterative and incremental software development begins with planning and continues through iterative development cycles involving continuous user feedback and the incremental addition of features concluding with the deployment of completed software at the end of each cycle.

3.3.4. d. Agile Model Agile SDLC model is a combination of iterative and incremental process models with focus on process adaptability and customer satisfaction by rapid delivery of working software product.

3.3.5. e. Prototyping model The Prototyping Model is a systems development method (SDM) in which a prototype (an early approximation of a final system or product) is built, tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can now be developed.

3.3.6. f. Rapid Application Development (RAD) Is a complete methodology, with a four-phase life cycle that parallels the traditional SDLC phases.

3.3.7. f. Joint Application Development (RAD) Joint Application Development (JAD) is a development methodology system originally used for designing a computer-based system, but can be applied to any development process. It involves continuous interaction with the users and different designers of the system in development.

3.4. 1.2.4 Identify appropriate life cycle models based on given scenario

3.4.1. The 7 phases of Software Development Life Cycle are planning, requirements, design, development, testing, deployment, and maintenance. Software Development Life Cycle consists of a complete plan explaining the way to develop, maintain and replace specific software system.

3.5. 1.2.5 Describe project management activities:

3.5.1. a. planning The project planning process is the main tool used to ensure that tasks are completed in timely manner. A project may best be defined as a venture taken to ensure that a deliverable is completed within a specific timeframe and that certain criteria or objectives are met.

3.5.2. b. scheduling A project schedule is a document collecting all the work needed to deliver the project on time. For example, most tools have task lists, which enable the manager to schedule multiple tasks, their due dates, sometimes the planned effort against that task, and then assign that task to a person.

3.5.3. c. monitoring Project Monitoring refers to the process of keeping track of all project-related metrics including team performance and task duration, identifying potential problems and taking corrective actions necessary to ensure that the project is within scope, on budget and meets the specified deadlines.

3.5.4. d. reporting A project report is a document that communicates the progress of aspects of the project, containing data relevant to that part of the project and the audience it's addressed to. Project management reports are something that you'll be generating regularly over the course of the project.