3A: issues rel. to proposed sol. Flashcards
what to think about regarding proposed solution of a new product
will solution provide enough advantages to be worth the time, effort, money involved?
considerations from client’s perspective
- does the functionality of existing systems exist in the foreseeable future
- will new systems meet future needs
- any existing similar solutions?
- how crucial is it? if not very, use resources otherwise
considerations from developer’s perspective
- required expertise
- resources required
- will product be able to be supported in future?
- staff + resources; will it affect other projects?
what should be considered prior to commencing design + implementation
different methods and approaches
each method/approach should…
be targeted at achieving the same set of requirements, as it allows fair judgement in choosing method/approach
existing software products
- should be researched, as usually more cost effective solution
- may be able to tailor functionality to user’s needs
- e.g. open source: can be altered or customized, AI: can be outsourced or bought through existing modules
considerations with methods of solutions
may be more than one way to solve problem:
- if software solution required, usually multiple solutions
- consultancy services examine different approaches/solutions to problems
what should be considered when comparing dev of new software with use of existing software
- social + ethical considerations
- legal issues including licensing considerations
- customisation of existing software products
- cost effectiveness
social + ethical considerations
- changing nature of work for users
- effects on level of employment
- effects on public
changing nature of work for users
intro of new products: affects nature of work, which should be considered
- get input from potential users
- if product = broad distribution, consult w/ industry associations/unions
employees: changing nature of work for users
when new products introduced, work may change:
- contracts may need re-negotiation
- employees may need more training
effects on level of employment
1970s: concerns that computers would replace people; but now there are more positions which replace labour-intensive jobs
reasons for new software systems
reduce a business’ cost:
- largest costs for businesses: salaries + wages, new software products designed to reduce employment in area
- think about cost saving + employee redundancy
effects on public
both positive + negative:
- large software systems may involve training for whole population + reluctance in older generation
- must consider how system will affect general public when defining problem
legal issues + licensing considerations
copyright!!! for both rights of dev + customer
- customer’s personal info must be safe from unauthorized access
legal issues regarding use of existing software
- contact other users of product
- consider level of support from dev, possibility of requesting new functions
- understand Ts and Cs
use of open source existing software
free of direct costs, do not usually provide direct support
- sometimes distributed commercially, professional support + training available
- may not be cost effective
customisation of existing software products
often a cost effective strategy for new functionality
- can be from dev to individual clients
- helps OG dev widen market
- common for tools in comm products to allow end user customization of screens + other functionality
customising open source software
used routinely to add new features
e.g. phpBB: popular open source product for online forums; modifications built as add-ons for added functionality
cost effectiveness
constaint of new software system: doesn’t fall within certain budget
cost effectiveness: predict costs involved in D+D to compare a new project with using/modifying existing product
areas of cost-effectiveness
- development hardware costs; new hardware used during dev
- development software costs; tools used during dev(CASE, languages, graphics, etc.)
- development personnel costs; staff
- outsourcing costs
budget for a software project
often from the client for whom the project is developed
things to think about when formulating budget
- available capital
- predicted sales for product
- cost savings as a result of the product
- ongoing customer support costs
- other costs
what is usually done when large projects go over budget
extra funds set aside for unforeseen circumstances, usually 20%
