Visible Systems Blog

John Nash

Recent Posts

DevOps Metrics

Posted by John Nash on Jun 9, 2021 11:31:22 AM

 

Why DevOps Metrics are Important to the Development Process?
 
DevOps Metrics

Developers are improving their development process by using DevOps metrics to capture data or indicators that measure the success of their development pipeline. Four Key DevOps metrics that Razor can track on an ongoing basis include:

1. Deployment frequency, how frequently code is released into the production stream [Monthly Reports, Weekly Reports, Releases Completed].

2. Lead Time, the time required from code to committed code to run successfully [Issues created, by Whom and When, Who is doing what, Who is most active].

3. Mean time to repair, how long it for a service incident to be repaired [Who is completing the most issues by User/Group/Universe].

4. Change fail rate, the number of changes that require a hot fix or a rollback in the value stream [Hot fixes by User/Group/Universe].

After your organization has built DevOps metrics into your workflow process. These metrics begin providing insights into what is happening your development pipeline.

Integrating the flow of the metrics into your workflow process begins to provide insights into what is happening in your development pipeline. These standard flow items are key operational components of the business.

Flow Metrics

1. Flow Velocity, simply tracks the number of flow items by type over some period of time.

2. Flow Distribution, this flow item is categorized based on a defined outcome.

3. Flow Time, measures the amount of time required for the activity to be completed.

4. Flow Efficiency, measures resolution time versus wait time and whether the trend is increasing or decreasing.

5. Flow Load, the flow load measures items in process, used to measure which value streams can lead to increased productivity.
 
Razor for DevOps

DevOps and Flow Metrics are crucial to value stream management. Value stream management is about delivering software products that create value. Software tools like Razor automate the value stream by capturing every aspect of the software development and delivery process, giving value stream managers the tools they need to to continuously improve software development. 

Source: What is Value Stream Management and Why it’s so Important?

For more details using Razor for DevOps, click here.
 

A Systems Analysis and Design Semester Project, A Stand-alone Versus Competitive Project

Posted by John Nash on Mar 18, 2019 9:57:47 AM

Below is an interesting research paper I found on the web on systems analysis and design by Ranida Harris of Indiana University Southeast that I think is worth reading. 

From the Abstract: Educators know the value of having a real world project for their Systems Analysis and Design courses. The author concludes that based on both the quality of work and student comments, that groups felt pressure to work harder, enjoyed the competition, and ultimately produced higher quality projects.  Teaching a systems analysis and design class can be challenging,  and many instructors have shown the efficacy in using a real world semester project.  This paper looks at delivering a systems analysis and design class differently. Rather than rely on student creating an individual project, they are teamed and compete, similar to an organization soliciting bids. Based on both the quality of work and student comments, revealed that groups felt pressure to work harder, enjoyed the competition, and ultimately produced higher quality projects. 

A Systems Analysis and Design Semester Project, click here to download

I thought I would share the link to this paper with you as it might add value to your course.

The Visible Analyst University Edition is a fully multi-user software tool compatible with any systems analysis and design course. With this tool project groups work together on an integrated projects. Even better, with this tool you can create a course that defines all of the lessons of phases of your semester project. If you are interested in learning more about the multi-user Visible Analyst University Edition, click here.

If you'd like to claim your FREE license to Visible Analyst, click here.

Lesson 7 from the Visible Analyst Tutorial

Posted by John Nash on Nov 29, 2018 1:04:03 PM

Entity Relationship Modeling (ERD)

Click here to see this video

Lesson 7 Screen

This lesson covers the basics of creating an entity relationship diagram and was created by Prof. Rhonda Richards.

In Visible Analyst’s terminology, a diagram containing a picture of all or a subset of your data is called a view. Each view can show an arbitrarily large or small part of your data model. You can show multiple views of your data model by including different combinations of entities and relationships on various diagrams. However, the entire data model, including the data elements composing each entity, is retained in the repository and can be accessed by creating a global view of the data model. This feature is explained in Lesson 7.

For more details on this lesson, please see pages 93-106 of the Visible Analyst Tutorial.

Let us know if you found this video useful!

Lesson 5 from the Visible Analyst Tutorial

Posted by John Nash on Nov 29, 2018 11:37:53 AM

This lesson was developed by Prof. Rhonda Richards can be found on pages 63-78.

Click here for Lesson 5

Lesson 5 Screen


Lesson 5 covers Diagramming and Repository basics.

The following topics are covered in this video:

1. CREATING A NEW PROJECT, page 63

2. CREATING A NEW DIAGRAM, page 66

3. EDITING A DIAGRAM, page 67

4. STYLIZING A SYMBOL, page 69

5. MOVING, CUTTING, AND PASTING A SYMBOL, page 70

6. ADDING LINES TO A DIAGRAM, page 71

7. SELECTING AND ADJUSTING LINES, page 72

8. ADDING CAPTION TEXT TO A DIAGRAM, page 73

9. OTHER DIAGRAMMING FUNCTIONS, page 75

10. DISPLAYING AND HIDING SYMBOL LABELS, page 78

11. CLOSING A DIAGRAM, page 77

 Let us know what you think!

 

 

 

 

 

 

 

 

 

 

 

placeholder_200x200

Subscribe Here!

Recent Posts