business project

SDLC (systems development life cycle)

1. Problem definition feasibility report why is it needed

1. Human Information requirements interview, questionnaires, watching, prototyping be on guard for “we have always done it this way”

1. Systems needs always begin with a picture, a process flow, a data flow diagram, structured decision points are identified sometimes referred to as a decision tree output is a proposal

1. Design the solution the entry, processing and exit points of data the importance of data organization (data dictionaries) definitions, and consistency in data naming and use Technical controls, backups, restores, security, roles of usage. The guidelines of how the design is maintained. Sometimes includes a disaster recovery plan.

1. Develop and document the system assume that a technician (programmer) who is different than the author will be able to understand and modify after implementation user help regulatory needs FAQs, Read Me files, training

1. Test and maintain the system unit, process related and volume testing and the capture of success or failure as evidence started by the developer but should also utilize clients as a reconnection from requirements to solution “traceability” time and effort spent in testing always pays off at this stage phases of SDLC are cyclical

Let’s discuss what change control is.

1. Implement and evaluate user training, data conversion sometimes called the transition evaluate did you achieve the objective as determined in the Problem Definition?

What’s more important humans or technology? Provide personal doctor’s office example.

Once implemented why do we maintain it?

Needs change

Security updates are needed

Bugs are encountered

Hardware or hosting strategies change. A large 10-12 month project should be able to be updated or upgraded in weeks.