Documente Academic
Documente Profesional
Documente Cultură
SDLC MODEL
First A. Mahfooz Rauf, Second B. Sarfaraz Solangi, and Third C. Haider Ali
Abstract- In the era of IT globalization, project paper is to prove the substantive gains in adapting a PM
management as a management discipline underpins much tool, with a number of precise features, concerning the
economic activity. In industries as diverse as choice of an SDLC model. This research paper covers all
pharmaceuticals, software and aerospace, projects drive these vistas and intents towards providing good resolutions
business. A project is a temporary endeavor, having a
defined beginning and end, undertaken to meet particular
goals, to bring some value added services. It includes
developing a project plan, defining and confirming the
project goals, identifying tasks, quantifying the resources
needed, and determining budgets and timelines for
completion. All these umbrella activities are catered in a
Software Development Life Cycle Model that describes the
stages involved in the development of a project. The
selection of SDLC model can vary depending on the nature
and requirements of the Project. On the other hand PM
tools are used in every project at each level to sort out tasks
and track project status, allocate responsibilities to
resources, plan and track project costs and resources. [1]
There are tons of models but all have very similar patterns. The software design is produced from the results of the
The general, basic model is shown below: requirements phase. Architects have the ball in their court
during this phase. The software's overall structure and its
nuances are defined. In terms of the client/server
technology, the number of tiers needed for the package
architecture, the database design, the data structure design
etc are all defined in this phase. The logical system of the
product is developed in this phase. The development phase
involves converting design specifications into executable
programs.. For a developer, this is the main focus of the
life cycle because this is where the code is produced.
Development may overlap with both the design and testing
phases. [3], [4], [6], [7], [8]
Testing
We can use Waterfall Model to assist in the engineering of Characteristics of Projects that fall under Agile Model
a project whose scope is well defined, i.e. the requirements
We can use agile development methodologies for projects
are well known which allow setting a schedule with
that are developed in iterative and modular approach, agile
deadlines for each stage of the SDLC. In such
development allows incorporating the high priority features
circumstances PERT (Program Evaluation and Review
as a sprint. Such approach also allows adaptation to
Technique) and CPM (Critical Path Method) are very
changes and requires collaborative efforts. The project is
helpful. Also the project should be such that it can be
developed in incremental phases, i.e. the entire system is
decomposed to the lowest level possible in terms of
not built at once instead parts of the system are developed
Activities and Tasks, thus making it possible to move
in single time. This way all such parts or features can be
through the phases of the SDLC in a strict order. The
managed and incorporated into a sprint on need basis.
project should allow the distribution of resources in the
Moreover the sprints become the perfect unit for planning
foundation phase with minimal chances that this
the project and we can set limit of each sprint and schedule
distribution will ever change again. This distribution can be
the activities of the sprint respectively. Projects that are
in terms of individuals or teams. Moreover the cost of the
time constrained can be tracked easily with the help of
overall project should be well clear without any ambiguities
daily scrum and observing the spring progress in terms of
at the beginning and this cost should not be altered much
sprint Burndown which is a timeline showing the sprint
during the project life cycle, i.e. there should be a least
actual progress against the estimated or likely progress.
chance that the allocated budget of the project will overrun.
Projects that include communication among different teams
[12]
or communication with remote teams can result in rapid
B. Agile Model changes that can be managed in Agile Model. [9]
C. SourceGear Fortress
Characteristics of Projects that fall under RAD Model Fortress provides all the version control features of our
Rapid Application Development is not appropriate for all renowned Vault tool - fast, secure remote performance;
projects. The methodology works best for projects that are
excellent concurrent development support; automated
(GUI) graphical user interface applications, where the
scope is small and work can be broken down into branching and merging; and 100% SourceSafe imports. But
manageable chunks. Along these lines project teams must by seamlessly integrating version control with bug tracking,
also be small, the project itself does not require too much of Fortress takes things several steps farther, yet still keeps
documentation. Also it must be suitable to develop the things simple. Fortress’s Line History function allows you
project in an iterative approach, which leads to multiple to zero in on any section of your code and see all the
versions of the software being produced. changes that have affected it over time. Changes to the rest
In order to achieve the above mentioned goals, RAD can be
of the file are ignored -- it’s as though each function had its
assisted with a project management tool that provides a
repository to maintain the versions of software, and own version control repository. Once you’ve found the
because of the iterative and prototyping approach, there history you’re looking for, Fortress can take you straight to
may arise a large number of defects and changes for which the bug report that triggered that change. All without ever
there is a definite need of a defect reporting tool. leaving your IDE. And it also offers the more-standard
History and Blame. Querying a large bug database can be
III Selecting Project Management Tools
frustrating. Fortress’s Clouds let you narrow a search one
A. MS Project 2007 factor at a time, quickly pulling out just the status, assignee,
milestone, etc. you’re looking for -- and never fill out a
MS Project helps you efficiently plan schedules, allocate
form along the way. [13]
resources, manage budgets, and set realistic expectations so
that the organization can achieve its long-term goals. It
IV. SUMMARY AND CONCLUSION
enables you to track project performance and the progress
during the entire duration of the project for a quick With all the characteristics of the models and project
understanding of the project management process. It management tools discussed above, we can come to the
provides visibility in work transactions, timesheets, and conclusion that in order to choose the right project
resource capabilities. You can build resource plans to co- management tool for a particular software development life
ordinate the recruiting and outsourcing strategies with long- cycle, on must choose a tool that maps the characteristics of
term business objectives. It enables you to assign resources the project and the development life cycle. Such choice
to tasks and manage conflicts over allocated assignments would lead to a PM tool that would assist in more phases of
easily. You can allocate work to the entire team collectively the life cycle than any other tool. This would yield in the
instead of assigning work to individual resources. Team objectives of the company achieved. Based on the similar
members can accept their individual assignments and analysis for the models and the tools discussed in this
indicate the time taken against the allocated assignment. [10] paper, it is recommended that MS Project 2007 is used to
manage a Project under Waterfall Model and ONTIME
AXOSOFT 2009 is used to manage a Project under Agile
Model and SourceGear Fortress is used to manage a Project
under RAD Model.
V. ACKNOWLEDGMENT
VI. REFERENCES
www.projectsmart.co.uk/the-importance-of-project
[1]
management.html
[2] www.pmforum.org/viewpoints/2007/PDFs/Naughton-8-07.pdf
[3] en.wikipedia.org
[4] www.sereferences.com/white-papers.php
[5] toostep.com/trends/types-of-sdlc-models
[6] www.allinterview.com/viewpost/29138.html
[7] www.answers.com/topic/systems-development-life-cycle
[8]
pages.cpsc.ucalgary.ca/~ayala/SENG/seng611/Assignment
s/LifeCycle.htm
[9] c2.com/cgi/wiki?EssentialAgileCharacteristics
[10]www.projectsmart.co.uk/features-of-microsoft-project-
2007.html
[11] www.axosoft.com/ontime
[12] www2.giac.org/resources/whitepaper/application/217.php
[13] www.sourcegear.com/fortress/literature/SG_Fortress_WP.pdf