New answers tagged

4

There are typically layers to requirements, especially if the software is complex or when specifying a system that includes both hardware and software elements. Depending on the complexity of the system, you can have any number of layers. I do disagree with your definitions, however. Requirements always address what the system does (functional requirements ...


1

I'm going to share my opinion, based on how my company assign staff to the projects. Obviously, every company has its staff management. First question is: Do I have an architect assigned to my project? If yes, then architect sould give to lead programmer the basics of the strategy. Or design it atleast. When architects are involved into a project, they are ...


-1

Yes, job shadow, however, in the end, draw dataflow diagrams. I've done it hundreds of times. I've never run into a business person who could not understand a graphically clear DFDs (i.e not spaghetti). If you can't draw the DFD, you don't understand the workflow. If the client can't understand the DFD, you've drawn it wrong, so revised it.


3

I have seen a different meaning to the term escrow as it relates to software development and contracting. Developer stores encrypted version of the software's source code with an escrow service. Escrow service periodically tries to contact the developer / contracting company to see if they are still alive / in business and servicing the software product. ...


4

That's one way to do it. Finding and paying a qualified arbitrator to determine that the delivered system meets the requirements of the MSA/SoW can be a problem. Furthermore, it's not unusual for requirements to change during the development process. I've seen escrow services used more often in the context of "contractor regularly deposits source code in ...



Top 50 recent answers are included