Slicing by CRUD or ISUD (AKA Slicing by Operations) Any User Stories involving a managed entity, such as a Customer, Order, Employee or Product, will almost always require some level of management functionality. This management functionality will provide the ability to perform a number of operations including at a minimum operation, such as Create, Read, …
A SQL Injection Attack is one of the many security issues that must be address when designing and developing applications that access a database. The injection vulnerability is potentially present on pages or forms where the user must enter a value to be submitted to the server. If the user input is not properly validated …
Slicing by Input Parameter (Datatypes) In most cases a business process or whatever function that the new feature is intended to automate requires some data to perform its actions. For the sake of this discussion we will refer to this data as Input Parameters. Data of different types in most cases will need to be …
A User Story is intended to be a method of communicating business or application requirements between potentially nontechnical customers, team members who are not developers and the development / operations teams that must implement the required application or features. In other words, the User Story needs to be understood by all but still provide enough …
Slicing by Acceptance Criteria Many User Stories contain a number of explicit or implicit Business Rules usually represented as Acceptance Criteria. If a User Story is so large or complex that we could not complete it in a single sprint we can consider slicing the User Story by its Business Rules or Acceptance Criteria. If we use …
To get started with Java Development and follow along with the ProDataMan Agile and DevOps samples and demos using Open Source tools you first need to download and install the Java Development Kit (JDK) You can find the link to download the JDK for you environment here: http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html Select your operating system and CPU type …
Slice by Test Cases Slicing User Stories by Test Case is useful when it is hard to break down an Epic based on functionality alone. With a large Feature or Epic, it is helpful to look at possible Test Cases as a way to break the Epic down into smaller chunks that can be completed …
Slicing by Workflow Steps Most anything that we would add to a solution and describe in a User Story is a process that has some sort of workflow. In most cases these workflows can be broken down into individual steps. A large User Story with several workflow steps can be broken down into smaller users stories …
First let’s talk about the acronyms CI, CD and CD… This whole CI / CD thing causes all sorts of confusion. First CI is Continuous Integration, for a definition see my previous post here: What is Continuous Integration. CD, now that’s a little trickier… CD is either Continuous Delivery or Continuous Deployment depending on where …
I am a firm believer that everything can and should be Agile! The days of analysis paralysis should be long behind us. Our customers and their attention spans move at internet speeds and you have 3 clicks or less to get their attention. Agile software delivery strives to deliver business value to customers quickly while …