• Seilevel Team

    Here’s the Team

    Welcome to our Seilevel Photo Op.

Non-Functional

Software updates and maintenance

Non Functional Requirements: Maintainability

Maintainability is how easy it is for a system to be supported, changed, enhanced, and restructured over time. Understanding up front how maintainable software needs to be for a certain project is important, due to its impact on your architecture. This impact makes maintainability an important non-functional requirement to consider …

Read More
non functional (interoperability)

Non-Functional Requirements (Interoperability):

In the sea of non-functional requirements, interoperability is defined as how easily a system can share information and exchange data with other systems and external hardware. Interoperability is often overlooked, much like other non-functional requirements because analysts and stakeholders often focus on the application’s functional requirements rather than the semantics of …

Read More

Ignore tasks, focus on decisions.

We all have our reasons for using a piece of software. Maybe it makes staying in touch easier, maybe it helps organize, or for that matter, make us money, maybe it’s just fun to interact with…whatever those reasons may be, the drive to get things done is not, and cannot …

Read More

Built to Kill

During a conversation with a lead engineer working on the Google self-driving car project, it was mentioned that the car would be programmed to consistently break the speed limit. On average, the car will travel 10 mph over any posted speed limit. Why design a car to deliberately break the …

Read More

Aligning User Expectations with Business Objectives

Projects with clearly defined business objectives can and do fail even if they deliver functionality that syncs closely with the business objectives defined for the project, but do not meet user expectations. This may seem counter intuitive at first blush since the primary purpose of any enterprise software development effort …

Read More

How Do You Approach an Analytics Project?

Business Analytics projects – where do you begin? In a previous post, Joy mentioned using decisions to prioritize requirements for business analytics projects. Beginning your project by identifying these decisions, uncovering business problems and mapping both to business objectives and the product concept will allow you to build out documentation. …

Read More

Measuring the Effectiveness of a Feature

There are two possible outcomes: if the result confirms the hypothesis, then you’ve made a measurement. If the result is contrary to the hypothesis, then you’ve made a discovery. Enrico Fermi There are four key factors that determine how effective any feature is in achieving its design objectives. They are: …

Read More

Defining Software Requirements to Handle Data Errors – Part 2

“To not anticipate is already to moan.” Attributed to Leonardo da Vinci As software requirements analysts, we have crucial decisions to make regarding those errors often considered rare. This is part 2 in a series of 3 posts on how to define requirements for error conditions, specifically data errors. Data Errors …

Read More

Defining Software Requirements to Handle Data Errors – Part 1

“The expected always happens.” Benjamin Disraeli, via Bram Stoker’s Dracula. As software requirements analysts, we have crucial decisions to make regarding those errors often considered rare. In this series of posts, I’ll discuss how to define requirements for error conditions, specifically data errors. Unlikely. Unexpected. Unpredictable. Random. Intermittent. Rare. Typical responses …

Read More