Beruflich Dokumente
Kultur Dokumente
A set of activities that applies to all software projects regardless of their size or complexity Includes activities, methods, best practices, deliverables, and tools that stakeholders use to develop and maintain information systems and software There is no ONE PROCESS STANDARD Matured organizations have more consistent processes Experience shows that well managed software processes lead to least cost software development One of the most well known framework is the CMM
IST321 Ch3 1
IST321 Ch3
Level 5 indicates most matured software development process Maturity level is considered as an effectiveness indicator
IST321 Ch3 3
Repeatable
Basic Project Management practices are used including tracking cost, and schedule Repeat previous success
Defined
Documented process of software management and engineering Standardization of process and engineering practices
IST321 Ch3 4
Optimizing
Continuous process improvement Defect prevention Technology change management Process change management Feedback loop
IST321 Ch3
IST321 Ch3
12
Phase Principles
Each phase is associated with a set of tasks Each phase has a set of deliverables Mile stones and budgets can be associated with these deliverables Each phase has some participants with well defined roles There are risks associated with each phase Output of one phase is generally the input to the next phase Presented sequentially, in reality, not
IST321 Ch3 13
Determine scope, size, preliminary budget, time frame Gathering information is necessary - quickly done with minimal determination The analyst often talks to key personnel at this stage system owner and technical leadership of IS organization Outcome: An initial feasibility report, with some alternative solutions, and initial project parameters Should we carry out feasibility for all systems?
IST321 Ch3 14
Information Gathering
Techniques
Sampling of existing documentation Research and site visits Observation of the work environment Questionnaire Interviews
IST321 Ch3
16
Sampling of Documentation
Objective is to understand policies, procedures, techniques and data used to complete business operations Type of documents to be studied
Standard reports, data gathering forms, procedure manuals Database and file system architectures Existing project dictionaries, documentation Organizational policies, plans as applicable No cook book approach exists, judgment is needed to select
Sampling can be used to select documents, however it is more desirable to have a sample of every document type
IST321 Ch3 17
IST321 Ch3
18
Disadvantages
Beware of the Hawthrone effect Observation time may not coincide with peak effort level Seasonality and cyclic patterns may be missed
IST321 Ch3 19
Observation should not lead to work disruption Necessary authorization must exist for conducting an observation session
IST321 Ch3
20
Questionnaire
The best method to collect responses from a very wide range of people Usually inexpensive, but one has to be careful about the response rates Lacks the depth and intimacy of observation, but benefits from the anonymity a respondent enjoys Questionnaires tend to be inflexible, and suffers from the possibility of missing important details Lengthy questionnaires are ignored Bias in the questions are highly undesirable
IST321 Ch3 21
Questionnaire
Questionnaires can be open-ended or structured Structured questions are easy to answer and analyze, but often the depth of understanding is sacrificed Open-ended questions allow more in-depth information gathering, but often prove difficult to analyze and aggregate
IST321 Ch3
22
Interviews
Perhaps the best method of information gathering since each topic can be studied in detail Time-consuming and often expensive Interviewer bias, if any, can seriously taint the collected data Format of interviews are similar to questionnaires open-ended vis-a-vis structured Interviewer should be well prepared, with subjects defined ahead of time Objectives must also be clearly defined
IST321 Ch3 23
Usually involves significant interaction with the user to find DATA, PROCESS, INTERFACE, and GEOGRAPHY requirements of the system Information gathering techniques are applied The information gathered is synthesized into a proposed system requirement model
IST321 Ch3 24
IST321 Ch3
25
IST321 Ch3
26
Design Phase
Often considered as the detailed design phase Precondition: Approved system architecture and systems requirement specification Focus is on components to be developed or integrated Major activities include
Detailed database design Detailed application program design Design of interfaces and dialogs
Classical methodologies may be used: structured charts, object-diagrams May employ CASE tools RAD or rapid application development is now being preferred for many systems
IST321 Ch3 27
Construction Phase
Detailed coding Unit testing Integration and System testing
IST321 Ch3
28
Implementation
Install at customer premises Acceptance testing Minor tuning as necessary
IST321 Ch3
29
Model-Driven Development
A number of models are used during the life cycle phases
Structured Analysis - a process-oriented technique used to model a systems requirements: Data Flow Diagrams Structured Design - A design tool used to transform structured analysis model to structured design models: Structured Charts Object-oriented analysis and design (OOAD) - Model is developed using objects and their interaction
Advantages
Better planning and documentation of the requirements Extensive use of graphical tools - tends to improve communication with users Alternative architectures are relatively easy to generate
Disadvantages
Tends to be complex for large projects
IST321 Ch3 30
RAD
Often uses prototyping approach Prototyping technique require that we build a prototype of the proposed system using modern tools rapidly The prototype itself may become the system, or may serve as the model for the system Activities
Define the scope Define, design, construct the database and UI Exercise the system Take feed back, modify, and reexercise Continue until users are satisfied Move on to the next level of scope and repeat process
Drawbacks? Advantages?
IST321 Ch3 31