Student Seminar Report & Project Report With Presentation (PPT,PDF,DOC,ZIP)

[attachment=4517]

---

ABSTRACT

---

PROJECT IDENTIFICATION AND SELECTION

---

[attachment=6217]
SYSTEM DEVELPOMENT LIFE CYCLE (SDLC)

SYSTEM DEVELOPMENT LIFE CYCLE

The Systems Development Life Cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project from an initial feasibility study through maintenance of the completed application. Various SDLC methodologies have been developed to guide the processes involved including the waterfall model (the original SDLC method). Documentation is crucial regardless of the type of model chosen or devised for any application, and is usually done in parallel with the development process. Some methods work better for specific types of projects, but in the final analysis, the most important factor for the success of a project may be how closely particular plan was followed.

For more information about this article,please follow the link:
http://elucidatarefs/sdlc.pdf

Capability Maturity Model (CMM)
• A bench-mark for measuring the maturity of an
organization’s software process
• CMM defines 5 levels of process maturity based
on certain Key Process Areas (KPA)
CMM Levels
Level 5 – Optimizing (< 1%)
-- process change management
-- technology change management
-- defect prevention
Level 4 – Managed (< 5%)
-- software quality management
-- quantitative process management
Level 3 – Defined (< 10%)
-- peer reviews
-- intergroup coordination
-- software product engineering
-- integrated software management
-- training program
-- organization process definition
-- organization process focus
Level 2 – Repeatable (~ 15%)
-- software configuration management
-- software quality assurance
-- software project tracking and oversight
-- software project planning
-- requirements management
Level 1 – Initial (~ 70%)
SDLC Model
A framework that describes the activities
performed at each stage of a software
development project.
SDLC Phases
• Systems Investigation
– Identify problems or opportunities
• Systems Analysis
– How can we solve the problem
• Systems Design
– Select and plan the best solution
• Systems Implementation
– Place solution into effect
• Systems Maintenance and Review
– Evaluate the results of the solution
Waterfall Model
• Requirements – defines needed
information, function, behavior,
performance and interfaces.
• Design – data structures, software
architecture, interface
representations, algorithmic details.
• Implementation – source code,
database, user documentation,
testing.
Waterfall Strengths
• Easy to understand, easy to use
• Provides structure to inexperienced staff
• Milestones are well understood
• Sets requirements stability
• Good for management control (plan, staff, track)
• Works well when quality is more important than cost or
Schedule
Waterfall Deficiencies
• All requirements must be known upfront
• Deliverables created for each phase are considered frozen –
inhibits flexibility
• Can give a false impression of progress
• Does not reflect problem-solving nature of software
development – iterations of phases
• Integration is one big bang at the end
• Little opportunity for customer to preview the system (until
it may be too late)


download full report
http://googleurl?sa=t&source=web&cd=4&ve...2Fsdlc.pdf&ei=tOl-Ta2eK8n0cLedrd8G&usg=AFQjCNGgz5jXITfeDYRHa-8wUYiH2UdxuA