tag:blogger.com,1999:blog-4384692836709903146.post1203325191897505577..comments2024-03-27T09:55:23.143-07:00Comments on Dispatch from the Digital Health Frontier: A Unified Software Development LifecycleJohn Halamkahttp://www.blogger.com/profile/04550236129132159307noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4384692836709903146.post-73138873945457186832013-03-21T19:16:20.775-07:002013-03-21T19:16:20.775-07:00I am impressed by this process. The large public ...I am impressed by this process. The large public HIT company I work for who shall not be named would do well to follow such a process. Often it feels to me as though are developers are way out of touch with the needs of our clients. Melissahttps://www.blogger.com/profile/11936267029552384766noreply@blogger.comtag:blogger.com,1999:blog-4384692836709903146.post-11679401847428153252013-03-20T04:32:48.035-07:002013-03-20T04:32:48.035-07:00Nice overview Dr. Halamka.
#3 is interesting to me...Nice overview Dr. Halamka.<br />#3 is interesting to me. Being in an infrastructure team, I see System Requirements Definition often overlooked or put off until just before project go-live and testing. This can be dangerous as long lead times can occur with purchases and configuration of infrastructure products required to make the project "go." Infrastructure, like business owners, developers and analysts, are really stakeholders as well and, in my opinion, should be involved as such ... earlier in the project. While I know it's pretty difficult to understand what your infrastructure requirements are before design decisions have been made, I think the two decisions should go hand-in-hand, thus reducing the risk that the infrastructure can't handle the new system and long, expensive, unplanned-for upgrades have to be made. My two cents as an infrastructure employee.Anonymousnoreply@blogger.com