160 likes | 301 Views
The Systems Development Life Cycle (SDLC). What do consultants do?. Bob Porter. Bob Slydell. Tom. BOB SLYDELL So what you do is you take the specifications from the customers and you bring them down to the software engineers? TOM That, that's right. BOB PORTER
E N D
Bob Porter Bob Slydell Tom
BOB SLYDELL So what you do is you take the specifications from the customers and you bring them down to the software engineers? TOM That, that's right. BOB PORTER Well, then I gotta ask, then why can't the customers just take the specifications directly to the software people, huh?
TOM Well, uh, uh, uh, because, uh, engineers are not good at dealing with customers. BOB SLYDELL You physically take the specs from the customer? TOM Well, no, my, my secretary does that, or, or the fax.
BOB SLYDELL Ah. BOB PORTER Then you must physically bring them to the software people. TOM Well...no. Yeah, I mean, sometimes.
BOB SLYDELL Well, what would you say… you do here? TOM Well, look, I already told you. I deal with the customers so the engineers don't have to!! I have people skills!! I am good at dealing with people!!! Can't you understand that?!? WHAT THE HECK IS WRONG WITH YOU PEOPLE?!!!!!!!
What do consultants do? • Consultants analyze a situation or a system. • They then offer solutions to IMPROVE the system or situation or CREATE a better one.
Systems Development Life Cycle (SDLC): • A way of creating a program or IT system. • It is the process that professionals use. • All of you use the SDLC whenever you create a program, but you probably aren’t aware that you are doing it. • There are 4 steps to the SDLC.
4 Steps To SDLC: • 1. Planning • 2. Analysis • 3. Design • 4. Implementation • Each step has a DELIVERABLE. • Deliverable: A formal summary for the client.
1. Planning Phase: • Someone at a company says: “A program needs to be built that will do my work for me!” • The company hires a team of people (usually consultants) that come in and they do the following: • Determine if the program needs to be built. • Figure out if it is possible to build the program. • Approximate the time needed to build the program. • Staff the project. • Create a project plan. This is the deliverable.
2. Analysis Phase: • Now it’s time to get to work. • Gather information: • What is the program that’s in place? (And how bad is it?) • Can the old program be improved upon or should we start from scratch? • Who will be using the new system? • What does it need to do? • When will it be used? How often? • A System Proposal is created that states what the new program will do. This is the deliverable.
3. Design Phase: • Figure out how the program will work. • Determine the interface. • Create the blueprint for the program. • Determine which person will develop which parts of the program. This is where methods come in handy because we can split up work. • Deliverable: • System Specification – Tells the client what the program will look like, what it needs, what it will do.
4. Implementation Phase: • Build the program! • Test it! • Install it! • Train the users. • Deliverable: The program or system!
Issues: • Will everyone be allowed to use the system at first? • Software glitches (bugs) • System support.