Developer Integrity: A system either supports or harms the people within it

Human beings possess an inherent fear of being taken advantage of by other people. Analysis allows a software developer to de-structure a system to identify its functions, roles, and environment. Object Oriented Analysis and Functional Analysis both present different options for how a software developer deconstructs and observes a system. In order to successfully design and organize a system, a software developer must take care to understand its surrounding environment and working parts. Object Oriented Analysis encourages a developer to consider the abstract things that make up a system. A developer considers all of the working parts in the environment in the observation. Alternately, Functional Analysis encourages a developer to consider what you want a piece of software to do and software developers create functions that allow a system to operate according to what you want the software to do. Object Oriented Analysis considers the different job responsibilities assigned to different roles. An important part of analysis considers the functionality that falls through the cracks when too many cooks are in the kitchen. If we fail to consider all of the moving actors and only consider how we want the system to operate, we miss a key portion of analysis. Customers need to be considered in the development of software. Behaving ethically in the workplace means that a developer works towards the good of others and does not harm them purely for monetary gain. A developer that wants to behave ethically and help others must consider the effect their software will have on the actors and roles within a system.

Object Oriented Analysis encourages a developer to not only create software that serves a specific function, but it demands a developer consider the effect their influence makes on the actors within the system. Considering the needs of others who operate within the system you are creating leads to positive customer relationships and performant systems. Failing to consider the needs of others within your system creates an environment of stress, fear, and negativity. Roles must be carefully assigned to actors with specific needs that need to be met in order to create a positive, organized system that others want to be a part of. Without Object Oriented Analysis, software developers may misunderstand the different actors and roles involved when creating software. A developer could assume that the actors are performing expected roles that they are responsible for when they are not currently following their predefined role in a system. When a system does not operate as intended later on in the development cycle, if a developer has not considered the individual roles of the system they may miss that the problem with the system is the roles are not being performed as expected. Customers must be considered and roles must be clearly defined to develop strong systems that meet the needs of others. Separating areas of concern into objects allows for improved analysis, because it allows a developer to deconstruct a problem into manageable parts. Addressing smaller concerns provides increased opportunity for resolution in an environment that others understand. The more a developer resolves the small problems in a program, the stronger the final system becomes. A system that forgoes clearly defined roles will contain cracks where the needs of others are undefined and unmet.

Analysis constitutes a developer preference. Analysis should always improve the functionality and environment of a system. Object Oriented Analysis and Functional Analysis can be utilized simultaneously to create comprehensive systems. While it may be true that software must be built to serve a specific function, a software developer should always consider the impact their program has on the actors that make up the system they are creating. In a world where software developers possess powerful knowledge that can greatly affect others, they must always remember to push to create a positive ripple effect in the world around them for the uplift of humanity.

Comments

Post a Comment

Popular posts from this blog

SalonAboutBeauty: Less Integration for Consistent Styling Across Components

Ensuring Consistent Variables Less provides several advantages for organizing CSS to ensure consistency across a website. The variables.less file defines reusable properties that allow a developer to easily communicate and maintain styles according to a style guide or theme.  The Less Web Development Cookbook describes properties in the variables.less file in relation to other programming languages: “Variables in Less are defined as the equivalent to statics in other programming languages. You assign a value to a variable once and use it everywhere in your code” (Meyghani & Jobsen, 2015, p. 50). It suggests that less allows a developer to set properties, such as colors and length, to variable names that retain their meaning and can be used everywhere in the code. Examples: @base-color: red, @primary: green.  By providing these definitions in a central location, developers create code consistency in all areas of the website. Creating an Organized File St...
Read more

Why “Human Error” Is Usually a System Design Problem

In complex systems, failure rarely comes from a single bad decision. It comes from problems that evolve slowly, cross boundaries, and remain unresolved while everyone involved behaves reasonably. Managing risk in these environments means managing trajectories, not just incidents. When ownership is divided strictly by role, function, or severity threshold, gaps are inevitable. Those gaps are where issues linger, age, and quietly accumulate risk, not because they were ignored, but because no one was responsible for carrying them forward end to end. This is common in healthcare, where delay is often necessary. A patient may require observation, referrals, or time to clarify diagnosis. The failure is not that care takes time; it is that the trajectory of care becomes fragmented. Each clinician escalates correctly within scope, yet no one owns the evolving picture across visits, domains, and decisions. The patient is evaluated repeatedly, reassured locally, and sent away without continuity ...
Read more

Challenges in Prosecuting Deep Web and Darknet Crimes: The Case of Ross Ulbricht and the Silk Road

  The deep web represents online information that is not easily accessible through search engines. Prosecuting crimes on the deep web is no more challenging than prosecuting crimes for any standard website because law enforcement can still track the user's location through a domain or IP address. Alternately, the darknet poses a challenge for law enforcement to address illicit activity because while the darknet is a web-based system, it is accessible only through the Tor protocol that encapsulates HTTP and HTTPS traffic, much like a VPN that hides a user’s location and identity. The Tor protocol, often called the Onion Router, contains methods for encrypting and routing traffic between peers. The purpose of the Tor protocol is to make web browsing anonymous by routing each request through multiple peers and altering encryption at various steps until the request reaches its destination. Subsequent requests may hop through different peers, making traffic appear random, unpredictable,...
Read more