Software Architecture: Use cases and requirements

  • 12 September 2017
  • RedSign
Use cases and requirements

Use cases form a technique for specifying functional requirements: use cases are helpful to specify what the system should do. A use case captures a contract with the stakeholders of a system about its behavior. A use case describes the system’s behavior under various conditions, as the system responds to a request from one of the stakeholders, called the primary actor.

97 things - Database as a Fortress

  • 10 February 2017
  • RedSign
Database as Fortress

The database is where all of the data, both input by your employees and data collected from your customers, resides. User interfaces, business and application logic, and even employees will come and go, but your data lasts forever. Consequently, enough cannot be said about the importance of building a solid data model from Day One.

97 things - Architectural Tradeoffs

  • 9 February 2017
  • RedSign
Vasa worship

Every software architect should know and understand that you can't have it all. It is virtually impossible to design an architecture that has high performance, high availability, a high level of security, and a high degree of abstraction all at the same time. There is a true story which software architects should know, understand, and be able to communicate to clients and colleagues.

97 things - Avoid Scheduling Failures

  • 31 January 2017
  • RedSign
Avoid Scheduling Failures

Failed projects can happen for a multitude of reasons. One of the most common sources of failure is altering the project schedule in midstream without proper planning. This kind of failure is avoidable, but it can require major effort on the part of multiple people. Adjusting the time line or increasing resources on a project are not normally of concern.