What I've found to help for small projects is to start with a very lightweight use case analysis.
What I've found to help for small projects is to start with a very lightweight use case analysis. For instance: * A small vision document: This project is a (short description) targeted at (accountants / small business / boy scouts). It solves this problem that the target market has: (pain point). Its main features are (what makes it a good solution / what differentiates it from the alternatives). * Main use cases: Some Trello cards with the main user-facing features, described at a very high level. * Technical overview: You seem to have that covered. E.g. it will be a web/mobile/desktop/command-line app built on (language/stack) with this architecture (microservices, MVC web app, client/server, etc.) storing data on (S3/SQL database/flat files). For a 1-person small project, don't overdo this part. Once you have this high-level overview of the project, try to implement the bare minimum necessary for the "happy path" of the main use case (i.e. without worrying about exceptional cases yet). Mock other aspects as necessary (e.g. authentication, dependent data sets, complex business logic, etc.) This will leave you with a huge technical debt that you'll need to crawl out of as move forward, but it will avoid analysis paralysis and over-architecting. For a more structured approach, one source that I recommend is "Use Case Driven Object Modeling with UML" ( http://www.softwarereality.com/UseCaseDriven.jsp ). It shows a technique to bridge the gap from the business requirements to the technical design and implementation.
Posted by facorreia on Jun 15, 2015, 9:08 PM
Tags
Related issues
- That's the biggest problem with iOS because Apple can be ordered to block them from the App Store and it would be instantly kill these pr...
- I'm intrigued about the "Trip Planner" being a top-level app.
- This asymmetry is IMO the biggest problem with AI-driven output.
- This is one of the most important objectives in software today.
- At least in Europe - these rouge corporations need to be reined in or just leave the market.
- I was skeptical, but this looks genuinely useful.
Raise real-world problems, find people facing the same issue, and discuss solutions.6,000 issues0 comments
hackernews (SaaS)
That's the biggest problem with iOS because Apple can be ordered to block them from the App Store and it would be instantly kill these pr...
I'm intrigued about the "Trip Planner" being a top-level app.
This asymmetry is IMO the biggest problem with AI-driven output.
This is one of the most important objectives in software today.
At least in Europe - these rouge corporations need to be reined in or just leave the market.
I was skeptical, but this looks genuinely useful.
Why has she gone through so many iPhones?
The biggest problem with Europe is the lack of innovation.
What I've found to help for small projects is to start with a very lightweight use case analysis.
What I've found to help for small projects is to start with a very lightweight use case analysis. For instance: * A small vision document: This project is a (short description) targeted at (accountants / small business / boy scouts). It solves this problem that the target market has: (pain point). Its main features are (what makes it a good solution / what differentiates it from the alternatives). * Main use cases: Some Trello cards with the main user-facing features, described at a very high level. * Technical overview: You seem to have that covered. E.g. it will be a web/mobile/desktop/command-line app built on (language/stack) with this architecture (microservices, MVC web app, client/server, etc.) storing data on (S3/SQL database/flat files). For a 1-person small project, don't overdo this part. Once you have this high-level overview of the project, try to implement the bare minimum necessary for the "happy path" of the main use case (i.e. without worrying about exceptional cases yet). Mock other aspects as necessary (e.g. authentication, dependent data sets, complex business logic, etc.) This will leave you with a huge technical debt that you'll need to crawl out of as move forward, but it will avoid analysis paralysis and over-architecting. For a more structured approach, one source that I recommend is "Use Case Driven Object Modeling with UML" ( http://www.softwarereality.com/UseCaseDriven.jsp ). It shows a technique to bridge the gap from the business requirements to the technical design and implementation.
Comments (0)
No comments yet. Start the discussion.