System Development Methodologies (2) Flashcards
List that tasks that are undertaken within each phases of the system?
Preliminary analysis
- feasibility study
- problem definition
Analysis -project requirements -new system System proposal (Project requirements) Old DFD reviewed Information gathering (JAD sessions, interviews, old documentation, viewing current process and activity)
Design
-Logical (e.g. receipt details) and physical design (e.g. physical receipt)
Focus on the transaction of data and not physical objects
New Logical (DFD, flow charts, pseudo code and ERD) and physical design
Story boards (design user interface)
Prototyping
Development
-hardware and software acquisition (Buying/purchasing)
-constructing and testing
Testing with the current working environment
Implementation
-change over method
Direct cut, parallel, pilot and phase
System documentation Training documentation Evaluation -performance evaluation -fault finding and correction
Testing
What are feasibility studies?
Feasibility study is an assessment of the practicality of a proposed project or system.
What are the 4 types of feasibility?
Economic feasibility - The likely benefits outweigh the cost of solving the problem which is generally demonstrated by a cost/ benefit analysis.
Operational feasibility - Whether the problem can be solved in the user’s environment with existing and proposed system workings?
Organizational feasibility – Whether the proposed system is consistent with the organization’s strategic objectives?
Technical feasibility - Whether the problem be solved using existing technology and resources available?
Social feasibility – Whether the problem be solved without causing any social issues? Whether the system will be acceptable to the society?
Discuss the data gathering techniques used by developers
Written Documents
The analyst may collect the information/data from written documents available from manual-files of an organization. This method of data gathering is normally used if you want to computerize the existing manual system or upgrade the existing computer based system. The written documents may be reports, forms, memos, business plans, policy statements, organizational charts and many others. The written documents provide valuable information about the existing system.
Interviews
Interview is another data gathering technique. ,The analyst (or project team members) interviews, managers, users/ clients, suppliers, and competitors to collect the information about the system. It must be noted that the questions to be asked from them should be precise, relevant and to the point.
Questionnaires
Questionnaires are the feedback forms used to collect Information. The interview technique to collect information is time-consuming method, so Questionnaires are designed to collect information from as many people as we like. It is very convenient and inexpensive method to collect information but sometimes the response may be Confusing or unclear and insufficient.
Observations
In addition to the above-mentioned three techniques to collect information, the analyst (or his team) may collect Information through observation. In this collect technique, the working, behaviour, and other related information of the existing system are observed. It means that working of existing system is watched carefully.
Outline some the implementation strategies that can be used within the system development life cycle?
Direct change over
Parallel run
Pilot run
Phase
Why does a developer need to create system and user documentation?
User Documentation: The user documentation is a complete description of the system from the user’s point of view detailing how to use or operate the system. It also includes the major error messages likely to be encountered by the user.
System Documentation: The system documentation contains the details of system design, programs, their coding, system flow, data dictionary, process description, etc. This helps to understand the system and permit changes to be made in the existing system to satisfy new user needs.
Discuss the importance of using Gantt charts and the pro’s
Pros:
• A Gantt chart organizes activities. It lists tasks and subtasks in logical groupings. It also shows who is responsible for each, and dates for starting and completing each task.
- The visual format is easy to read and understand. Gantt chart timelines give managers and team members a visual overview of when activities will occur, and whether they are dependent upon completion of other tasks.
- It helps to set reasonable time frames. Breaking down activities into detail and assigning a timeline to each creates a better, more accurate.
Discuss the importance of using Gantt charts and the con’s
Cons:
• It can become too complex for larger projects. A good project management software program, such as SmartDraw, won’t have trouble handling a large project. However, if you find that your project is too large for your Gantt chart to function well, consider breaking it into multiple Gantt charts.
- It can be somewhat inflexible. This is a complaint commonly heard from managers who use inflexible project management programs, or try to create their own Gantt charts by hand or using a spreadsheet. SmartDraw lets you view and edit your Gantt chart in a mind map, assignment, or timeline view. Easily make changes to any one and all of the others are updated, automatically, thus alleviating the inflexibility issue.
- It must be constantly updated. Projects involve surprises and changes must be made. SmartDraw is designed to make these changes as quick and effortless as possible.
What are Program Evaluation Review Technique (PERT) charts?
A PERT chart is a project management tool used to schedule, organize, and coordinate tasks within a project. PERT stands for Program Evaluation Review Technique