S/W Design Issues that MUST Be Fixed on New Site
Posted: Sun Jun 17, 2012 2:19 pmHow short memories...we all must be North American.
Well, here in Europe I am taking a broader view.
1. Implement a professional change management process including ops, devel, and test environments
2. Develop software artifacts that are software engineer-quality
3. Catalog all software and module use cases--one artifact for user features, one artifact for database calls, one for all other APIs
4. Construct a development schedule and follow a software design process--not "code and load"
5. Find a way to collect, prioritize, and assess risk/return on user feature use cases--let's stop coding by mob (board) rules
How about that--instead of "get rid of the grass" and "rename teams" so that the damn software is available when we pay our money. Not to be disparaging, but here we are again with collective myopia and an all-too-willing recipient in Bernie.
Sorry--no personal jabs here;just frustration
Well, here in Europe I am taking a broader view.
1. Implement a professional change management process including ops, devel, and test environments
2. Develop software artifacts that are software engineer-quality
3. Catalog all software and module use cases--one artifact for user features, one artifact for database calls, one for all other APIs
4. Construct a development schedule and follow a software design process--not "code and load"
5. Find a way to collect, prioritize, and assess risk/return on user feature use cases--let's stop coding by mob (board) rules
How about that--instead of "get rid of the grass" and "rename teams" so that the damn software is available when we pay our money. Not to be disparaging, but here we are again with collective myopia and an all-too-willing recipient in Bernie.
Sorry--no personal jabs here;just frustration