What do you think of my process model for small projects - "one person projects". Do you have any good ideas or improvements? Did anyone find it useful?
This is a simple model that I used when I got a small software project on my hands. Not small enugth to only write the code. Some common steps are removed as they were not necessary. I don't go into detail on anything as this only is the general steps that I used.
As this is a very small project working on the different steps can be made as required, but it's good to do much of the requirement engineering first as I hope you already know.
Requirement engineering
Find out what the software should do, elicit requirements. Talk with users/clients, give them a draft of the specification and make a new one after you got there comments.
-> Requirement specification paper (User cases, Functional requirements and so on)
Design engineering
Find out how to create the software, test code and se if it works, write down things you plan on using later and how it works.
-> Design specification paper (Programming language, functions/methods, how to do everything you need to do to create the software)
Write code
Put everything together
-> Source code -> something you can run (exe-file?)
Testing
You and the user/clients test the system to se if it works as intended.
User manuals paper
-> Instructions and help for the users of the software
There is so much information about coding so little about Software Engineering.