Comments for Michelle Yaiser

Comment on Getting Back to It by Tony Brown

Tony Brown — Mon, 22 Mar 2010 14:28:38 +0000

I look forward to taking more of your classes, this one sounds interesting.
It’s great that I found this sight, I love the resources here and I’m sure this will
help me in my endeavors to becoming a web developer/ designer (still figuring out where I fit in )

Comment on Best Practices for Designing RIAs by David Lance

David Lance — Fri, 19 Mar 2010 17:16:38 +0000

Requirements Technical Writer – building a job description

Postulate #1: The thorough gathering of requirements is defined as: “The gathering and recording of details pertaining to what the customers want the application to be and to do. This includes nuance. Subtlety. Attention to the smallest detail.”

Postulate #2: Requirements must be exhaustively recorded, then carefully organized and written into a set of deliverable documents. The audience for these is the team of programmers and developers who will write the code and build the application.

Postulate #3: A technical writer who is schooled in programming methodologies and object-oriented processes and design patterns can best translate and organize those customer requirements into verbage that can be transformed by software engineers into modules and functional components.

Postulate #4: In a Flex development project, the requirements technical writer will:

1. Meet with customers to capture requirements.
2. Draft a set of requirements, review them with customer base and gain their approval.
3. Mock up the UI of the application in Photoshop or Illustrator wireframes. Get customer approval.
4. Deliver those wireframes to a designer with instructions for building them in Illustrator and then in Catalyst. (Pay attention to layers.)
5. Gain approval of the Catalyst UI from the customer base.
6. Write the requirements in terms of the design patterns that will be used by the programmers.
7. Deliver to the programmers a full set of requirements docs ( Functional spec; External spec; Internal spec; Design spec; Process spec) together with the Catalyst-generated Flex files.

Comment on Best Practices for Designing RIAs by Dave Lance

Dave Lance — Fri, 05 Mar 2010 11:48:41 +0000

http://www.adobe.com/education/instruction/teach/ria.html?trackingid=DYDOY

Comment on Best Practices for Designing RIAs by Dave

Dave — Tue, 12 Jan 2010 00:03:36 +0000

http://www.adobe.com/devnet/flex/articles/fig_pt1.html

Comment on Best Practices for Designing RIAs by Dave Lance

Dave Lance — Mon, 11 Jan 2010 13:37:03 +0000

Hi Michelle. Keep them coming. This is great!

Comment on Best Practices for Designing RIAs by Adam Fehnel

Adam Fehnel — Mon, 11 Jan 2010 12:57:12 +0000

I can attest to these guidelines being equally valuable in web development. If you’re more into HTML than flash like me, just replace the word application with “website” in your mind and these make a incredibly helpful read.

Thanks Michelle!

Comment on Getting Back to It by Dave Dawson

Dave Dawson — Wed, 06 Jan 2010 20:31:47 +0000

Michelle, Good to see you posting again! I'd recommend checking out The Elements of Typographic Style by Robert Bringhurst. That book completely changed the way that I look and think about type, both in print and on the web. I'll be checking out Fluid Web Typography on your recommendation. Good luck with the new class!

Comment on Coffee-Stained Resources by Dave Lance

Dave Lance — Thu, 10 Dec 2009 19:07:25 +0000

Here is a book that describes how to read “actively.” I am due to read it again.

http://www.amazon.com/How-Read-Book-Touchstone-book/dp/0671212095/ref=sr_1_1/184-9496254-4323155?ie=UTF8&s=books&qid=1260471867&sr=1-1

Comment on Requirements – Part 1 by Dave Lance

Dave Lance — Thu, 10 Dec 2009 17:03:13 +0000

http://dlance.blogspot.com/

Comment on Requirements – Part 1 by Dave Lance

Dave Lance — Thu, 10 Dec 2009 16:39:54 +0000

Both Dilberts are perfect. Are you ready to get to work?