At my company I have seen a lot of bad software development practices over the years, so I have created a set of software development guidelines to help establish a set of best practices and baseline software requirements. I am publishing a series of experts from those guidelines here so that I might get some useful feedback that will help improve them.
Before development begins a source code repository needs to be created in an established source code repository area. Source code repositories must reside on a mass storage devices, such as a NAS or SAN, that is regularly backed up and maintained by the server group. Source code repositories must reside on equipment maintained outside of the development group.
At my company I have seen a lot of bad software development practices over the years, so I have created a set of software development guidelines to help establish a set of best practices and baseline software requirements. I am publishing a series of experts from those guidelines here so that I might get some useful feedback that will help improve them.
The platform specification, sometimes referred to as system requirements, should clearly describe all of the technologies that will be utilized in order to implement the solution. The specification should include the programming language, the development tools to be used and the client and server systems to be developed for.
<At my company I have seen a lot of bad software development practices over the years, so I have created a set of software development guidelines to help establish a set of best practices and baseline software requirements. I am publishing a series of experts from those guidelines here so that I might get some useful feedback that will help improve them.
The requirements specification should detail all of the processes and functionalities that the finished software should contain. This specification should include both functional specifications and non-functional specifications. The functional specification should employ use cases that describe the users interaction with the system (Graphical User Interface, Reporting Requirements). And, the non-functional specification should include any constraints not imposed by the user (Database Requirements, performance requirements, quality requirements).
At my company I have seen a lot of bad software development practices over the years, so I have created a set of software development guidelines to help establish a set of best practices and baseline software requirements. I am publishing a series of experts from those guidelines here so that I might get some useful feedback that will help improve them.
Every application, including internally developed applications, being used in the Company should have an application owner. This needs to be established prior to development. This designation should include a title or position as well as a proper name. In the event that the original application owner leaves the company, it should be clear who will inherit the role of application owner.
At my company I have seen a lot of bad software development practices over the years, so I have created a set of software development guidelines to help establish a set of best practices and baseline software requirements. I am publishing a series of experts from those guidelines here so that I might get some useful feedback that will help improve them.
No code should be written until a plan is defined.
At my company I have seen a lot of bad software development practices over the years, so I have created a set of software development guidelines to help establish a set of best practices and baseline software requirements. I am publishing a series of experts from those guidelines here so that I might get some useful feedback that will help improve them.
The intent of this document is to establish guidelines for software development which should help reduce total cost of ownership in the long term, ensure quality and consistency across the North American region, and implement a set of checks and balances between the various IT groups that improve operational transparency and reduce organizational risks.
I enjoy programming and creating great applications for users to electronically track and store their data, but the users will invariably want me to create reports for them from the data which we collect, and I do not enjoy this at all. It is tedious work, and it is never ending. There are always new ways to calculate or format the data which result in request to change the existing reports or add new reports. This is just not a good use of my time. So, I frequently try to expose the data to the users so that they can access it using Excel and create their own reports from there.
In one particular case I wanted to have an inline bar graph to visually show how each of the rows in an Excel spreadsheet related to the other rows. What I was looking for was a sideways candlestick chart of sorts. After some searching I found a solution built into Excel. It is possible to use the REPT function to repeat a character a specified number of times. My favorite solutions are the simple ones, and this is about as simple as it gets, here is an example: =REPT(“█”,L8) The image shows an example of the results.
At work I maintain some databases that are updated on a daily or weekly basis from a master data source. I inherited a stored procedure that would clear the data and then import the new data, but occasionally there would be problems with the import that would leave the data table empty. Also, the new data set from the master system only includes active records, so I would not have a way to maintain data that is no longer active. So, to improve things and make my job easier I created a Microsoft SQL Server DTS (Data Transformation Services) package that would automatically insert new records and update existing records
Christopher
