velox
Retired
13. Why is the quality of products developed using the prototyping approach likely to be lower than similar products developed using the structured approach?
-
Finished your HSC? Check out our University Discussion, Non-School forums or help out next year's HSC students! -
YOU can help the next generation of students in the community! Share your trial papers and notes on our Notes & Resources page
software development approaches (1 Viewer)
- Thread starter velox
- Start date
Hmmmm tough question, perhaps because when you move from the prototype to evolving the it into a working system, generally alot of the things from the prototype are extended on, and maybe the structure of the prototype initially was poor, structured prototype go step by step and have a higher quality rate because of how formal it is, and how things are taken in steps and most errors eliminated at each step as it progress's on
velox
Retired
ah ok thanks 
wat about the role of a systems analyst? wat do they do?
wat about the role of a systems analyst? wat do they do?Systems analyst work closely with the development team and with the actual client, he/she does all the managing between getting the right ideas of how the system should be, also delegating tasks etc and project management, and making sure the project is running fine, milestones being met, and re-arranging time if mile stones arent met, etc...Originally posted by wrx
ah ok thanks
Beaky
You can read minds?
- Prototyping misses the design and analysis stages of the software development cycle. These two stages are were most errors and refinement occur in terms of systems design.
- Lacks formal evaluation methods and testing that the software development approach goes through. Thus more errors occur.
- Lacks formal evaluation methods and testing that the software development approach goes through. Thus more errors occur.
velox
Retired
ah kool thanks pplz
velox
Retired
soz i got another question....
13. Do you think the end user approach is really software development? No real programming of any significance need takes place, so to call it software development is overstating its significance. Discuss
13. Do you think the end user approach is really software development? No real programming of any significance need takes place, so to call it software development is overstating its significance. Discuss
Well yes and no... it depends how big the project is... my family doctor made a program for his surgey himself, made within MS Access, and it was fairly complex, and just because it was a customised off the shelf solution it doesnt mean its not considered software development, it was just more flexible and easier to make in Access, but its still a piece of software made. So perhaps in this question i guess it's based on the scale of the project, whether or not its big enough to be classified software development, like wise if u made a form in VB and just slapped buttons and controls on it and it did very minimal things, i wouldnt classify that as software development.