Technical Resources

Software Design

The Software Design effort is a comprehensive software development methodology to collect and document the details of a custom software solution. It is intended to organize all the technical aspects of the solution and consists of the following deliverables:

  • Functional Design – describes the features/functions the system will provide including system business case, objectives and goals. In addition, reporting/output requirements for the proposed system and associated tools/solutions necessary
  • Data Design – The data model and data dictionary to support the functional requirements
  • UI/UX Design – defines all aspects of the user experience, screens, user interface, navigation and set the expectations of what a person will experience with the system
  • Technical Design – Defines the more technical aspects of the proposed solution including hardware/software platforms, development tools, and the distribution platform.
  • Solution Options/priorities – Software solutions often have multiple components, sub-systems and functionality that has varying degrees of priority to the business. If possible, Black Line breaks the entire solution into phases so Business Leaders can evaluate and provide guidance on priority to the business
  • Construction timeline/costs – Based on solution options and construction priorities, Black Line can produce a detailed timeline and budget to accomplish the system (and Business Leader) goals.

See Software Development Expectations for more details

Service Group
  • Software Development
Technical Value Propositions
  • Data Quality
  • Performance
  • Stability
  • Standards
Black Line Value Propositions
  • Access
  • Architecture-Design
  • Availability
  • Configurability
  • Cost Reduction
  • Decreased Hassles
  • Economic
  • Flexible-Creative
  • Improved Top Line
  • Information
  • Innovation
  • Integration
  • Performance
  • Product Quality
  • Productivity
  • Reduced Effort
  • Risk Reduction
  • Scalability
  • Simplify
  • Strategic
  • Technical Stability
  • Time Savings

Why does this matter for your business?

Black Line Engineers operate most effectively if provided with detailed specifications from which to code, solve and guide their development efforts. The software design process defines the details of the Client’s experience, business logic and overall expectations of the system being developed. The Software development process often has gray areas of requirements and decisions need to be made real-time and having a specification to work from dramatically increases the success.

The Software Design documentation is part of Black Line’s values of transparency, doing what we say and at the price we agreed to. Fixing the cost of the development effort provides appropriate accountability to maintain appropriate efficiencies. It is also essential to the planning, execution and successful management of the construction project

What value does this add to your business?

If servers, or server related, technologies are not available the modern organization cannot function. Regardless if the server technologies are on-premise, cloud-based or virtual. As the name implies, Server technologies “serve” data, features, secure, and organize the digital assets of an organization.

  • Technical Stability
  • Responsiveness
  • Availability
  • Risk Reduction
  • Information

What common problems does this solve for your business?

Missed expectations of a software solution, overlooked components, unexpected costs, over budget, underperformance of solution, quality issues, lack of solution transparency, incomplete deliverables

Why do you need a solution?

Similar to a blueprint for a home, building or other construction project having accurate expectations is critical for both the builder and the Client to measure success. Software development is simply the automation of business processes “thought up” by business people to solve business problems. The challenge is capturing business logic, convert logic into code, then verify and validate the problem was solved with automation.

By having a detailed specification to collect these requirements, how it will be built, what the business people will experience, the cost to build…the odds of success go up significantly. If during construction there are disagreements as to scope, the “blueprint” can be leveraged to negotiate a mutually agreeable solution.

What can you and your business expect from this service?

Business Leaders can expect:
  • A detailed specification intended for the comprehension of a business leader to address a business need. While there are technical components of the design deliverables, the bulk of the effort is intended to define system functionality within the business context not a technical one
End Users can expect:
  • If a end-user or employee possesses subject matter knowledge on the business processes targeted for automation, they will be involved in defining the requirements. The best people to provide solution details are the people experiencing the challenges day-to-day and know what the rules, exceptions and process expectations need to be. In addition, these same subject matter experts will be part of validating the design and testing solutions

How does Black Line do it better?

Black Line balances the need for a detailed specification with the reality that not all business logic can be captured in a document. Typical business systems, especially those that are mature, have many nuances to them that would require more time/budget than a project has. Therefore, Black Line’s approach is to capture 80% of the functional and business rules during the design process and factor the other 20% into the construction effort. It also provides a vendor-agnostic design deliverables that can be used for communicating functionality, goals and objectives to other business leaders and stakeeholders.

This approach reduces the time frame of the design, allows the software development team to produce working aspects of the system quickly while addressing undocumented requirements on the fly. This method allows us to produce smaller (functionally viable) components of a system in a sequence that produces the final system in “stages”.

Black Line also provides the Business Leaders with options to implement aspects of a system to match the priorities of the business. For example, a proposed system may have 6 major components, of which, 4 are critical and 2 that are less important and can lag to subsequent versions/phases.

More Questions or Want to Talk?

Let’s get started by understanding your business’s needs.

We start with a conversation to deeply understand your wants and needs. Only by truly diving into discovery can we uncover the best solutions.

Let’s Talk >

Content That Can Make You Think Differently

We don’t just look at IT differently, we think about it differently. We see the small details, and also the big picture. We see ideas before they come to life.

Look at some of our always-updating posts and articles, and you just might start thinking differently about your IT.