Sdl c Examples
-
Upload
cris-dalumpines -
Category
Documents
-
view
226 -
download
0
Transcript of Sdl c Examples
-
7/27/2019 Sdl c Examples
1/53
SDLC Project
Examples
-
7/27/2019 Sdl c Examples
2/53
Planning Phase
Example 1
-
7/27/2019 Sdl c Examples
3/53
Project Plan
The system we are developing for our business is awebsite that we will use to update our customersabout our next location as a social network as well assell our products and merchandise.
As a business we need to be able to manage ourwebsite effectively, update our information quicklyand clearly communicate our information to ourcustomers.
Our website will allow customers to become
members of our business, login into our site,browse products and information and contact thefounders of Forensic Fountain.
Plan
System Requirements
Critical Success Factors
Feasibility Studies
Analyze
Design
Develop
Test
Implement
Maintain
-
7/27/2019 Sdl c Examples
4/53
Project Plan
Our critical success factors include:
A data-driven website
Easy to navigate home, order, and other pages
of the site
Clear flow of the website
Effective communication to the founders
Used to analyze customer feedback and makechanges
Plan
System Requirements
Critical Success Factors
Feasibility Studies
Analyze
Design
Develop
Test
Implement
Maintain
-
7/27/2019 Sdl c Examples
5/53
Project Plan
For Forensic Fountains system we decided to
conduct the following feasibility studies:
o Cost-Benefit Analysis This study will allow ourcompany to determine if the benefits of running the
click part of our click and mortar business outweighthe costs of running an online operation and will tellus whether to keep that part of our business or not
o Schedule Study This feasibility study will help ourbusiness because we have a lot of dates and events tokeep track of due to the fact that we are a travellingbusiness. A schedule study will help us determine ifwe can meet all of our obligations as a company.
Plan
System Requirements
Critical Success Factors
Feasibility Studies
Analyze
Design
Develop
Test
Implement
Maintain
-
7/27/2019 Sdl c Examples
6/53
Project Timeline/Milestones
November 2, 2011 Business requirements and project plandrawn up and completed
November 5, 2011 Sent database model to programmingcompany
November 10, 2011 First basic prototype completed and
under revision November 12, 2011 Second prototype completed
November 13, 2011 Database received from programmingcompany
November 13, 2011 Website completed and ready for
system testing November 16, 2011 Final product approved for launch
November 20, 2011 User documentation due
November 21, 2011 Website opened to the public, databasefully functional
Plan
System Requirements
Critical Success Factors
Feasibility Studies
Analyze
Design
Develop
Test
Implement
Maintain
-
7/27/2019 Sdl c Examples
7/53
Planning Phase
Example 2
-
7/27/2019 Sdl c Examples
8/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
CheckPoint Rush is based around women dirtbiking. Our
company wants to start a website that will familiarize our
current and potential clients with what we do, what kind of
products and services we offer, and what our location is. Our
customers will be able to purchase products online through our
website, and download special training videos.
We will keep our customers up to date with all the latest
information regarding our products and special offers and
discounts.
Customers will also be able to ask questions, and expect
answers within 24 hours.
Project Plan
-
7/27/2019 Sdl c Examples
9/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Project Plan
Our company will focus on the following critical
success factors:
a website which is easy to navigate
customers will be able to contact us in case
they are having problems with placing orders
all required information will be in place
easy download option for training videos.
-
7/27/2019 Sdl c Examples
10/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Project TimelineNovember 12, 2012 Project plan completed and business
requirements identified
November 15, 2012 Database model is finished and sent to the
programmers
November 17, 2012 Website design completed and training
videos due
November 19, 2012 Premier prototype is completed and under
review
November 20, 2012 Page for custom orders designed and
competed
November 26, 2012 Final product completed and user
documentation due
December 1, 2012 Website is launched and available to the public
-
7/27/2019 Sdl c Examples
11/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Feasibility Studies
Our company will conduct the following feasibility studies:
Economic feasibility study will allow us to compare costs
related with creating a website with forecasted benefits.
By doing this analysis, we will be able to determine what
parts of website should or should not be excluded from
original design.
We will perform operational feasibility study in order to
see if the website will accomplish all objectives. It will
help us find out on what parts of the project we need to
focus more, and how to optimize them.
-
7/27/2019 Sdl c Examples
12/53
Analysis Phase
Example 1
-
7/27/2019 Sdl c Examples
13/53
Project Analysis Business
Requirements
Our online system will:
1. Be easy to navigate from login to checkout
2. Have an online ordering and payment system
3. Present information in a clear andunderstandable way to customers
4. Allow employees to use customer information toanalyze business performance
5. Allow the generation of reports regardingdifferent aspects of the business
6. Allow customers to contact the business withcomments or concerns
Plan
Analyze
Business Requirements
Process Diagrams
Buy vs. Build
Design
Develop
Test
Implement
Maintain
-
7/27/2019 Sdl c Examples
14/53
Project Analysis
The two processes we chose to diagram are a customerorder and contact us.
Due to the fact that our website will be a large part ofour sales, showing the customer order process will help
you understand how a customer will go through oursystem and also help us identify where potentialproblems might arise.
In addition, because we are a travelling business we donot have a concrete location where customers can
come and share their concerns with us. Therefore, thecontact us process of our business will be crucial to oursuccess (or failure) as a business. A social networkingfunction would also help cohesion.
Plan
Analyze
Business Requirements
Process Diagrams
Buy vs. Build
Design
Develop
Test
Implement
Maintain
-
7/27/2019 Sdl c Examples
15/53
Customer Order Process
When our customers first visitour site they will see our homepage. In order to place anorder, they will need to sign in
as members of our site.Customers will be promptedfor their User ID and Password.If they are new to our system,they can create a profile (freeof charge) by setting up a UserID, password, and some briefinformation. Once they havedone that, the system will
either verify their information,or will reject it as an invalidlogin and request they entertheir information again. Oncethey have been accepted, theyare free to browse through allof our products and selectwhichever fits their fancy.Once a product has been
selected and a customer isdone shopping, they willproceed to checkout wherethey will enter their paymentinformation, confirm theirorder and their method ofreception, and send in theirorder for packing.
Verify user
Enter User ID and
Password
Invalid
Login
Add User ID,
Password and
Confirm
New User
Product
Selection
Customer order
and payment
Products
Existing User
Order review and
Payment
Information/Type
Shipping or Pick-up
Order
Confirmation/
Package
Destination
Customer ComputerSta
-
7/27/2019 Sdl c Examples
16/53
Buy vs Build Analysis
Our business relies mainly on the building
side of a buy v. build scenario. We plan on
hiring someone to build our website in-house but do not plan on using a canned
website development system. We will be
able to have more options as far as being
able to modify and update our website if
we did this.
Plan
Analyze
Business Requirements
Process Diagrams
Buy vs. Build
Design
Develop
Test
Implement
Maintain
-
7/27/2019 Sdl c Examples
17/53
Analysis Phase
Example 2
-
7/27/2019 Sdl c Examples
18/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
We chose to diagram customer login process and the
enrollment process.
Our customer database is going to be a big part of our
website because it keeps track of all of the different
accounts as well as the information in each account
including:
Purchases
Class enrollments
User history
User interests
Project Analysis
-
7/27/2019 Sdl c Examples
19/53
-
7/27/2019 Sdl c Examples
20/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Buy VS Build Analysis
Our company has performed buy vs. buildanalysis, compared costs and benefits related to both
options, and come up with a conclusion that its in our
best interest to build our own website.
Our company has already hired employees who are
experts in technology and design. Therefore, we are
confident that the final product will live up to our highest
expectations.
By building our own website we will be able to make any
necessary changes and alterations as they come up.
-
7/27/2019 Sdl c Examples
21/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Process Diagram: Enrollment Process
During the enrollment process,
customers will be prompted to login
or create a user name. Then they will
be presented with the available
courses. From there they will have the
option to browse our instructor
profiles and select the instructor and
the course that they like the best.
After they have selected their course
they will be required to make a down-
payment to hold their seat in the
class. They will pay the remainder of
the cost when they arrive for the
class.
-
7/27/2019 Sdl c Examples
22/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Process Diagram: Login Process
The login process will enable our customers to create
their own accounts, through which they
will be able to place orders for standardized or customized
products, ask questions, apply for
training lessons, and download training videos.
Current users will be able to access their accounts by
inputting their user names and passwords.
New clients will be able to sign up by inputting their
personal information, like name, address
and contact information, and choosing a unique user
name and password to access their
accounts.
Our company will run a database of all users information,
and it will guarantee confidentiality.
By maintaining a database, we can learn about customers
preference and inform them about
specific discounts and offers regarding those products.
-
7/27/2019 Sdl c Examples
23/53
Design Phase
Example 1
-
7/27/2019 Sdl c Examples
24/53
Plan
Analyze
Design
System Model
ER Diagram
Navigation
Develop
Test
Implement
Maintain
System Model - Website
Log InFind Us
Catalogue
Contact Us
Fan Pictures
Home
Comments
Logo BUSINESS NAME
Body
-
7/27/2019 Sdl c Examples
25/53
Plan
Analyze
Design
System Model
ER Diagram
Navigation
Develop
Test
Implement
Maintain
CUSTOMER
ORDER
CUSTOMERORDER
Payment
Destination
-
7/27/2019 Sdl c Examples
26/53
Plan
Analyze
Design
System Model
ER Diagram
Navigation
Develop
Test
Implement
Maintain
ShoppingCart
HOME
Log In
Checkout
Continue
shopping
Abandoncart
Web Site Navigation
Catalogue A Product
Yes
Add to cart?
No
Find Us
Fan Photos
Contact Us
-
7/27/2019 Sdl c Examples
27/53
-
7/27/2019 Sdl c Examples
28/53
CheckPoint Rush [Logo] : Slogan
Login
Products
Training Facilities
FAQs
About Us
Our Riders
Videos
Photo Gallery
Upcoming Events
Blog
Join Our Team -- Policies -- Contact Us
Picture
Slide Show
(Body)
System ModelPlan
Analyze
Design
Develop
Test
Implement
Maintain
-
7/27/2019 Sdl c Examples
29/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
CUSTOMER
PAYMENT
CLASS
REGISTRATION
ORDERS
PRODUCTS
CheckPoint Rush Company Database
VENDORS
-
7/27/2019 Sdl c Examples
30/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
CheckPoint Rush Website Navigation
Login
Products
Training
Facilities
FAQs
About Us
Our Riders
Videos
Photo Gallery
Upcoming Events
Blog
Follow us on Twitter
HomePage
Customer Account Account History
Create New Account
Shopping Cart
Products
Continue Shopping Check Out
Training FacilitiesInfo
Riders Bios
Indoor
Outdoor
Our Bios
Company Info
Media Page
SlideBomb
News
Posterous Spaces
Twitter
-
7/27/2019 Sdl c Examples
31/53
Development Phase
Example 1
-
7/27/2019 Sdl c Examples
32/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Website Prototype
We chose this prototype because it is
easy for the customer to navigate. We
also included fan photos because we
wanted our customers to be recognizedfor their contributions to our business
success.
-
7/27/2019 Sdl c Examples
33/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Website Prototype
-
7/27/2019 Sdl c Examples
34/53
Development Phase
Example 2
-
7/27/2019 Sdl c Examples
35/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Our company is satisfied with how the initial prototype looks
like. The website is streamline and very
easy to navigate. Our customers will not have any trouble
finding the information that they need, which
is one of our main requirements. The design of the website is
very appealing. The combination of colors,
pictures and text makes it look very professional and fun at
the same time. It shows off the adventurous
spirit, and excitement related to dirt biking.
Prototype
-
7/27/2019 Sdl c Examples
36/53
-
7/27/2019 Sdl c Examples
37/53
Testing Phase
Example 1
-
7/27/2019 Sdl c Examples
38/53
Plan
Analyze
Design
Develop
Test
Website Test
Implement
Maintain
Screen / Form Tested
Date Tested
Home page
November 17, 2011
Tester Name of Tester
Test Condition Expected Results Actual Results (Circle one)
Pass Fail
Pass Fail
Pass Fail
Pass Fail
Log In to the
System
A Customer/fan is able to
log in with a username and
password and access the
system in a personalized
matter.
The system was able
to match my user
name and password
Fan Photo
Additions
The fan photo addition
uploads external photos to
the system.
The photo database
wouldnt fully add
photos to the
appropriate folder
Cart Memory
Limits
The customer database
should be able to keep a
cart in memory for two
weeks.
The cart was able to be
accessed during random
instances over the
lengths of two weeks.
Check Out Customers receive aconfirmation email with a
receipt and conformation of
their method of reception.
The system generated
an email that was sent
to the customer inbox.
-
7/27/2019 Sdl c Examples
39/53
Testing Phase
Example 2
-
7/27/2019 Sdl c Examples
40/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Screen / Form Tested
Date Tested
Check Point Rush Shopping Cart Operations
11/14/2012Tester Mary Smith
Test Condition Expected Results Actual Results (Circle one)
Payment Methods The system will take the
Information of the payment
(i.e. credit card, gift card)
and process it correctly
The system was able to
Take the payment
Information to process and
Complete the transaction
Pass Fail
System Log in Customers are able to enter
Their log-in info and system
Will recognize it and bring
them to the correct account
System was not able to
Match username and
Password to the information
Stored in the database
Pass Fail
Shopping Cart
Performance
Shopping cart will keep track
Of all items and will navigate
Through website while
Shopping cart is open
The shopping cart kept track of
all items and navigated through
The Website without losing the
Items in the cart
Pass Fail
Check out Once customer is done
Shopping the system will
Navigate them to correct pages
To complete transactions
The system completed the
Check out process after
The payment cleared
Pass Fail
Testing
-
7/27/2019 Sdl c Examples
41/53
Implementation Phase
Example 1
-
7/27/2019 Sdl c Examples
42/53
Implementation - Training
Forensic Fountain is a travelling company and as such the amount of employees will be fairlysmall, thus our main training method is mainly based on a one-on-one interaction with atrainer. The company will not hire large groups of individuals, so group training will not berequired. Online training would also be beneficial because the training information would bearchived, thus making it available to employees as needed. For one-on-one training, eachemployee will spend a day of training with a founder or high level employee learning thesystem.
USER DOCUMENTATION: Training manuals will be developed and available to employees asneeded. In addition, we will incorporate a train-the-trainer program people new to oursystem after the initial training. There will also be a FAQ area for employees to access asneeded.
Plan
Analyze
Design
Develop
Test
Implement
System Training Implementation
Method
Maintain
-
7/27/2019 Sdl c Examples
43/53
Implementation
Our business will be implementing a plunge
conversion method. We do not have a
current website, so plunge makes the most
sense for our business.
Plan
Analyze
Design
Develop
Test
Implement
System Training Implementation
Method
Maintain
-
7/27/2019 Sdl c Examples
44/53
Implementation
Example 2
-
7/27/2019 Sdl c Examples
45/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
We will implement this system through a semi continuous training program.
This means that a group of employees will attend meetings on a bimonthlybasis to learn what is changing within the system so they can train the rest of
the employees. This will help keep the management and usage of the system
the same.
Parallel conversion will be used so we can have a system to fall back on just
in case a problem does arise with the new system. This will ensure that wewill not be completely out of a system if something does end up failing. We
will keep the system up through production and maintenance by using the
training program stated above.
User documentation will include a user manual. This manual will give
detailed records on how everything within the system works. Any systemuser will be able to look in this manual if they have any question and they will
be able to find exactly what they need to do in order for the system to run
properly.
Implementation
-
7/27/2019 Sdl c Examples
46/53
Maintenance Phase
Example 1
-
7/27/2019 Sdl c Examples
47/53
Maintaining Forensic Fountain
The founders of the company along with acouple two IT specialists will be in chargeof performing changes to the system as
problems arise. We will have a help desk tofield both customer and employeequestions. The founders will also be incharge of changing the system format to
customize the experience based oncustomer and employee feedback.
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Performing Changes
System Maintenance
Maintenance Schedule
-
7/27/2019 Sdl c Examples
48/53
Maintenance Cont. Our adaptive maintenance will be handled by the owners of Forensic
Fountain and will mostly entail them managing the layout and flow of thewebsite in order to better accommodate customers and employees and thegrowing needs of the business.
Our corrective maintenance responsibilities will be handed over to the few ITspecialists the company has hired to make sure that the system runssmoothly and any defects are eradicated quickly and without problems.
The perfective maintenance aspect of our company will be based heavily onthe feedback from our customers and employees. Once we have sufficientdata to warrant a change, those changes will fall under the adaptivemaintenance process and be handled by the same personnel.
Our preventive maintenance will be monitored by our IT specialists, as is ourcorrective maintenance and will be based on trends produced by our
maintenance schedule and commonly reported problems from within andoutside of the company. This maintenance will also be based on metrics
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Performing Changes
System Maintenance
Maintenance Schedule
-
7/27/2019 Sdl c Examples
49/53
Maintenance ContPlan
Analyze
Design
Develop
Test
Implement
Maintain
Performing Changes
System Maintenance
Maintenance Schedule
During the first 3 months of operation:
Daily scans to check for any problems with the navigation, design, and other major areasof the site
Routine weekly system testing to make sure system and databases are running smoothly
Customer simulation by employees to test ease of system
Effective April 1: Monthly scans of the system to ensure everything is still functioning highly (test links,
documents, product database, etc)
Periodic customer simulation to asses the quality of the website
Quarterly updates to the system
Bi-annual Deep checks/scans of databases perform data cleansing activities
Monthly metrics will be ran to determine efficiency and effectiveness of site
Company reports at the end of every quarter to assess performance and website quality
Customer feedback, questions and complaints will be read and dealt with as soon as they occur.
-
7/27/2019 Sdl c Examples
50/53
Maintenance Phase
Example 2
-
7/27/2019 Sdl c Examples
51/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
In order to maintain the website and the system, weekly,
monthly, and quarterly scans will be ran. These scans will
certify that all the data in the system is up to date and
accurate. If an issue is flagged, the operators and specialists
that work on the system will fix it. If any updates need to be
done, they will take care of that as well. Examples of itemsthat need to be updated include coupons/promotions, current
company information, videos, our social media accounts, our
blog, and any other information within our system that needs
to be continually updated to keep our customers informed
about what is going on with our company. Along side keeping
our informed, we will respond to any customer questions or
concerns as they come up.
Maintenance
-
7/27/2019 Sdl c Examples
52/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
For adaptive, our technical team will keep tabs on new
technologies and update our system correspondingly.
For corrective, we will correct any imperfections that
present themselves within the data in our database or any
out dated information that comes up on our website.
For perfective, we will have our team continuously try to
make our site more efficient and effective for our
customers by improving our site navigation.
For preventive, our team will also be constantly be
monitoring for issues with our software and upgrading any
problems they may find to help our system stay healthy.
Maintenance
-
7/27/2019 Sdl c Examples
53/53
Plan
Analyze
Design
Develop
Test
Implement
Maintain
Our technology team will work on a regular maintenance
schedule.
Daily:
Check basic site functions
Check links
Check system stability
Check database functioning
Weekly:
Run cleansing software on database information
Check site traffic to help maintain the right level of
functioning
Monthly: Check system server stability
Check system for bugs
Maintenance