Research and Development (R & D) are important activities in the software development process. They ensure that the software developed can adjust to the changing industrial and technological patterns and cover a wider scope of the market for the interest of the company. However, as R&D happens, it is paramount for the developers to ensure that the software created is highly secured and interests of the clients considered and worked on. Additionally, it is crucial to empower the created software to enable every interested user to navigate with ease regardless of the device used (laptops or mobile devices). For these reasons, this paper seeks to address concerns about networks and security in addition to the development approaches that would best suit Big Metal Manufacturers.
First, a combination of network security to safeguard Big Metal both internally and externally is paramount (Tankard, 2011). The modern technological advancements have brought about advanced threats to most organizations’ data and distant applications. For instance, one issue that the developers should consider carefully is the quality of cyber-security programs they create (Tankard, 2011). Evidently, use of virtual teams in Big Metal calls for a tightened security approach. Additionally, the main aim of these programs is to internally and externally coordinate firms and vendors respectively, function with suitable resources, empower and support attempts to manage the rampant evolving threats while dealing with the customer wants (Satzinger, Jackson and Burd, 2011).
Further, the developers should use ssessment of risks and mapping, oversight and vendor contracting, synchronization of data privacy, fraud detection, technology efforts, and anti-money laundering as points to be noted in the development process (Tankard, 2011). First, assessment of risks and mapping help in giving special consideration to dangers associated with distant and variant mobile approaches (use of virtual teams), systems of funds transfer and devices. Moreover, it is appropriate and mandatory to conduct an assessment of the legal, regulatory, financial and technical risks to give room for limiting their occurrence.
Furthermore, developers should also undertake oversight and vendor contracting to take care of the technical specifications and business requirements of the system (Satzinger, Jackson and Burd, 2011). Again, if possible, Big Metal’s contract is required to address various means used to ascertain security (through anti-virus software, invasion detection, network inconsistency detection, event handling and security details, and configuration managing) (Tankard, 2011). In addition, the regulatory issues that are requisite in the contract include safeguarding against unauthorized utilization, entry, and revealing of customer information, timeframes for maintaining records, and adherence to the rules regarding conveyance of information in addition to media by Big Metal to increase their customer trust. Another consideration for developers is synchronization of data privacy, fraud detection, technology efforts and anti-money laundering through fraud mitigation unit and credit risk management (Tankard, 2011).
On the other hand, the best approach for development to be used by Big Metals would be a standard approach (Satzinger, Jackson and Burd, 2011). In the Structured System Development (SSD), structured approach refers to the joint techniques of structured design, analysis and structures. This approach results into a program with one starting and termination with each progression having a solitary construct among a concatenation of program disclosures, a choice point where a sole or alternative set of instructions functions, and an iteration of a set of instructions (Satzinger, Jackson and Burd, 2011).
One of the most applicable development philosophy is agile (Satzinger, Jackson and Burd, 2011). Agile development refers to a set of guidelines meant for advancing information set-ups in unspecified, intensively adjusting environment. Additionally, the advantage of using agile for development is its compatibility with any methodology pertaining to system development (Satzinger, Jackson and Burd, 2011). Nonetheless, the methodology that best suits agile is lean development methodology. This methodology seeks to create a change-tolerant software. Further, it incorporates the idea of dynamic stability. Besides, lean development is governed by twelve major principles. First, the greatest priority of lean development is to grant the customer utmost satisfaction. It also seeks to give the greatest value for the money (Satzinger, Jackson and Burd, 2011). Additionally, success is based on active customer involvement. For this case, incorporating mobile phones into the system whereby ease of access is given gives customers an easy and frequent time of visiting. Again, this methodology states that everything is subject to change; thus, different requirements may be represented as dynamics change. Finally, each LD task is a team attempt (Satzinger, Jackson and Burd, 2011).
Besides, agile development has several advantages. Customers’ interests are represented due to their regular involvement (Koch, 2011). Consequently, it helps the customers identify easily with the project since they feel part of the development process. Secondly, there is increased agility, and since the world is prone to changes daily, the agile method has an iterative lifecycle, which ensures every change is well accommodated (Koch, 2011). Additionally, use of agile makes the customer expectations to become a reality since customers are regularly consulted as fore-stated to ensure that the project ends up looking like their expectations. Furthermore, the development team is motivated, and their productivity increased (Koch, 2011). The interaction between the team and the customer creates satisfaction between the two parties, which gets them motivated. Finally, this development process results in the production of high-quality software by ensuring; fitness for use and purpose, the absence of defects, and a reliable and maintainable product.
On the contrary, the agile method has some disadvantages. First, requirements arise and develop throughout the process (Nerur and Mangalaraj, 2005). As a result of the many requirements that may pop up, it may be difficult to expound on a business case for a project which is possibly dangerous. Again, where software deliverables exist, it is complicated to assess the pathway required in the initial steps of developing the software (Nerur and Mangalaraj, 2005). Finally, there is an absence of emphasis on crucial designing and documentation (Nerur and Mangalaraj, 2005). Besides, agile development has several risks such as resistance to embrace agile principles, lack of cooperation between the developers and the customers, and fading spirit of agile as time passes by (Nerur and Mangalaraj, 2005).
In summary, agile development is the most applicable systems development method. Any product made from the interaction of customers and developers is likely to perform well and be easily accepted. Additionally, choosing agile would perform better for Big Metals in this instance. The reason for this is the IT Director for Development should ensure for a safe and user-friendly product that caters for the interest of parties.