Re-think the Project's design

[savage...@gmail.com]

Our previous iHacky design was more towards revolving around the
hackystat framework, where a user would be able to share and view
information from the sensorbase in a social way. This was our
previous focus which made iHacky revolve around hackystat. But the
professor wants iHacky to be more independent and use hackystat as a
add-on or a side thing that the user can exploit at their leisure. So
I think we must redesign the system to make iHacky more of a
standalone application that is not centered around hackystat but
instead use hackystat as a aid for the application.

Please let me know what the team thinks about this...

[Jon Lao]

We need a foundation for iHacky.

What can the Facebook users get from iHacky.

Connecting them with other hackers? Getting help thru the iHacky
community (once established)?
Sharing project ideas? or coding styles?

Right now we are pretty vague on everything.

We'll gotta hit that sweet spot ... let's not stop thinking new ideas.


Thanks
Jon

[Philip Johnson]

This might be a good time for you all to revise/create some Use
Cases. I know that you probably just thought of them as a "homework
assignment" previously, but I think if you actually got serious about
creating, reviewing, and improving them, you would find that this is
the fastest way to get clear about what a useful set of requirements
for your system should be, and the order in which you want to add
capabilities, and how to get past "vague" ideas like "connecting with
others" and move into "concrete" system capabilities to implement.

The semester is ticking away, folks. Don't waste it.

Have you communicated with Josh Stupplebeen? He seemed to have some
good ideas.

[Jon Lao]

I did email Josh like a week or so ago. No replies yet though.

May be my email got blocked.

:/