home -> academy -> IT processes, standards
On this page > Introduction <> SCRUM and other... <> Management, misc <> DevOps practices <> Project Management <> Quality Assurance <> Programming source-code quality <> What leads to...


Somewhere, SdLC has lowercase "d", because software-life-cycle does not focus on the development so much.

Some good industry practices, processes, standards keep the SoftwareProduct_vendor /SaaS_provider competitive and successful on the market. Some could be vital for staying in the market at all.

Information security standards, for example PCI-DSS payment card industry-data security standards, include both:
- network security during data-transfer and network-access protection while the data resides on the PRODUCTION environment itself;
- local read /write access ability. Encryption of the data itself.

There is also ILC information-life-cycle term. The Data Governance program handles ILC.

Another important abbreviation - "ITIL (Information Technology Infrastructure Library), is a set of practices for IT service management (ITSM) that focuses on aligning IT services with the needs of business". It includes Release and deployment management. Also, "The trend toward a closer working relationship between development and operations is termed: DevOps." The automation of these practices seems to be important. What do you think?

SCRUM and other agile approaches

"Scrum is easy to understand, but hard to master!". Other popular process-management-systems (set of principles and practices) are Kanban, Lean, RUP. If you would like to explore these, feel free to search for them in the web.

Three screen-shots from "Applying UML and Patters", a book of Craig Larman. 1 of 3:
2 of 3:
3 of 3:

Management, misc

Usually, the business system /team /organization is stronger when there are more easy-replaceable employees. That's why, it is written in home>academy>Oracle> Implement ETL systems, IM field section - "Besides, eventually, the stakeholders (client and managers) will be more independent of key developer-employees.".

In some organizations, there is no maturity towards Data Governance programs. One reason could be, because it is not well understood and the investment in it is not prioritized. Another reason could be, that the resulting improvements bring efficiency, but also transparency. Eventually, the last could not be wanted, because it can threaten someone's authority, position, financial interest. Some ?professionals manage the so called their "own personal job-security plan /project". I would say, like Hristo Stoichkov (soccer player) does - "I am no like this". The following is relevant home>academy>Demand of IM services

DevOps practices

Wiki - "DevOps (a clipped compound of "development" and "operations") is a culture, movement or practice that emphasizes the collaboration and communication of both software developers and other information-technology (IT) professionals while automating the process of software delivery and infrastructure changes.".
Often, these practices involve usage of Cloud services.

Project Management

The section /page "home>academy>Case-study projects>TatyaBank_cardPayments_csProject2" has the following sub-sections - "End-to-end DW construction plan by stages", "Practices", "Project tools, for example". This information helps in planning the SDLC, end-to-end process.

Quality Assurance

"QA is not an act, it is a mental discipline, which results in high-quality software without much testing effort."

Source -> SoftServe forum.

Programming source-code quality

Do write good source code, by exploiting the following intuitive /natural source-code-quality requirements, bunch-listed:

1. Basic rule 1 - have one logic implemented only at one place and RE-USE;
2. OOA-D-P - capsulation (attributes+methods/behaviour), inheritance, polymorphismus; interfaces describe behaviour;

3. Multi-tier architecture, low-coupling, each tier/layer (repository) should contain sourceCode/logicImplemented/components relevant to its/layers definition/purpose.

For example, three/3 tires by/* two/2 component categories/types= 6 + 1(Business entities) + 1 (DB) = 8 component types:

tier / layer def descr
presentation UI UP User access/UI, User process UI + stateful/session objects, View and ?!Model (from MVC design pattern)...
business logic BW BL Business workflow stateless logic, Controller (from MVC) ...
BE Business entities objects/types transferred between the tiers ...
data access DA SA Data access, Service agents supporting ObjectRelationalMapping, persistence; webService clients ...
DB database MVC's model, together with the previous (DA)
4. Do it agile - multiple iterations, the feedback from each iteration feeds the next one, the floating (fixed only for short-term) responsibilities motivate the employees/programmers additionally.
5. Proper error /exceptions-handling;
6. Kiss - keep it short and simple. One function - one (max 3) screens code;
7. Continues integration and many other processes, strictly followed;
8. ... other design patterns and best (well-accepted) practices.

What leads to success?

Tedx's answer: