Quote:
Originally Posted by 3rd_gear_Ted
CMMI level 3 - document minimums , or its not really a SW project
User requirement specifications - user interfaces - work processes
System Architecture - key issues - owner principle stories
Implementation Strategy - quality criteria - unit task specs -unit test cases
Pre release defects are on YOU
Post release defects are on the OWNER
What so hard???
|
I would kill for specs like that at times, other times I'm happy for the freedom I have
My work tickets are usually like -
"The other college in town needs to give us a list of student ids to mark as being accepted into/graduated from their program for a certain term/year. Make it happen"
or
"HR needs a dynamic PDF created when someone completes a training course"
While those types of tickets are easy (and the OPs project sounds like one of these - "retrieve file from $location, parse, validate, and store") due to the freedom I have in how to actually solve the problem, it sucks when tickets are like
"Update and rewrite the transient student system from our 25 year old tech stack to the new hotness" just due to the technologies involved in the current implementation (IBM's VG/EGL anyone?) but also due to the lack of documents on what the state expects as a REST api or what the state provdes as a API - apparently there is some magical gateway service that when we are done we'll be able to map the two systems together....