13.07.2015 Views

Java™ Application Development on Linux - Dator

Java™ Application Development on Linux - Dator

Java™ Application Development on Linux - Dator

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

272Chapter 11Balancing Acts: An Imaginary Scenario11.6.2 Back at His DeskBob is now back at his desk p<strong>on</strong>dering the c<strong>on</strong>versati<strong>on</strong> he had with Ellen.“These are not like the requirements we learned about in my software engineeringcourses,” he muses. “I’ve got that sketch of the UI and a brief descripti<strong>on</strong>of its functi<strong>on</strong>ality. But there seem to be so many unanswered questi<strong>on</strong>s.”So what is Bob supposed to do? He could go back and try to get more“face time” with Ellen, and ask lots more questi<strong>on</strong>s. Sometimes that’s a smartthing to do. Other times such repetiti<strong>on</strong> is seen as annoying and a sign of aslow-witted analyst, never mind how obscure the initial discussi<strong>on</strong>s were orhow many times some<strong>on</strong>e changed their mind about what they want. You willhave to judge each situati<strong>on</strong> as you encounter it. At some point, though, youhave to deal with whatever informati<strong>on</strong> you’ve been given, and try to make thebest of it.So where do you turn? The next best things to do are to begin to documentthe requirements as you understand them, to prototype a soluti<strong>on</strong>, andto start getting buy-in from other stakeholders. Each of these activities mayhelp bring out more requirements, but that’s not a bad side effect.11.7DOCUMENTING, PROTOTYPING, AND STAKEHOLDER BUY-INOnce a project is started, the design must be documented. A prototype may bebuilt to validate and refine the design. Finally, every<strong>on</strong>e with a stake in thesuccess of the design has to be brought up to speed and needs to agree <strong>on</strong> whatis to be built.11.7.1 DocumentingAfter such a c<strong>on</strong>versati<strong>on</strong>, it’s smart to try to get your thoughts down <strong>on</strong> paperas so<strong>on</strong> as possible. Some of what gets said will fade with time, so work quicklyto capture what you can of the requirements that were spoken. Even if you haveto leave lots of blanks, keep moving and get as much of the major requirementswritten down as you can, even if they d<strong>on</strong>’t sound very formal or polished.Then go back, revise and edit your statements, filling in the blanks where youcan. Sometimes you will need to ask others to get the answers to fill in theblanks. Other times you can use your own judgment and initiative to providean answer. Out of this process with its subsequent rewrites will come therequirements document.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!