The CIS 110 “Software Process” 
For all 110 projects, your instructor is the Client and you are the Developer.
The client will give you a list of project requirements and you will deliver a solution on time that meets or exceeds the requirements.
Always Meet the Requirements
Here’s your task as a developer:
- Understand the requirements (asap). If something does not make sense, clarify this by asking questions in class.
- Write and test the code to meet the requirements, to the best of your ability.
- Budget time for help hours visits. When the last help hour of the week ends, you are on your own.
- Don’t miss the easy points– if the client asks for a file named hello-world.html, then name your file exactly that. (It might make no difference to you to put the images in a different folder, but it will make a big difference to the client.)
How your Work Will be Assessed (SQA)
Your work will be evaluated on how well it “meets the requirements”. This is Software Quality Analysis (SQA).
Your job is to deliver what the client wants, when the client wants it.
If you depart from the requirements, the client will say, “That’s nice, but it’s not what I wanted.”
This is the last thing you want to hear from a client. (Think, “Goodbye, Holiday bonus!”)
You are assessed on how well you meet the requirements, and that includes the meeting the deadline.
Get the Client’s Approval for any Changes you Make
If you have a good idea to improve the requirements, discuss your proposed changes with the client.
One of the most valuable services a software developer can provide the client is to help clarify and/or improve the specs.