3A: issues rel. to proposed sol. Flashcards

1
Q

what to think about regarding proposed solution of a new product

A

will solution provide enough advantages to be worth the time, effort, money involved?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

considerations from client’s perspective

A
  • 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

considerations from developer’s perspective

A
  • required expertise
  • resources required
  • will product be able to be supported in future?
  • staff + resources; will it affect other projects?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

what should be considered prior to commencing design + implementation

A

different methods and approaches

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

each method/approach should…

A

be targeted at achieving the same set of requirements, as it allows fair judgement in choosing method/approach

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

existing software products

A
  • 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

considerations with methods of solutions

A

may be more than one way to solve problem:
- if software solution required, usually multiple solutions
- consultancy services examine different approaches/solutions to problems

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

what should be considered when comparing dev of new software with use of existing software

A
  • social + ethical considerations
  • legal issues including licensing considerations
  • customisation of existing software products
  • cost effectiveness
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

social + ethical considerations

A
  • changing nature of work for users
  • effects on level of employment
  • effects on public
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

changing nature of work for users

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

employees: changing nature of work for users

A

when new products introduced, work may change:
- contracts may need re-negotiation
- employees may need more training

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

effects on level of employment

A

1970s: concerns that computers would replace people; but now there are more positions which replace labour-intensive jobs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

reasons for new software systems

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

effects on public

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

legal issues + licensing considerations

A

copyright!!! for both rights of dev + customer
- customer’s personal info must be safe from unauthorized access

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

legal issues regarding use of existing software

A
  • contact other users of product
  • consider level of support from dev, possibility of requesting new functions
  • understand Ts and Cs
17
Q

use of open source existing software

A

free of direct costs, do not usually provide direct support
- sometimes distributed commercially, professional support + training available
- may not be cost effective

18
Q

customisation of existing software products

A

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

19
Q

customising open source software

A

used routinely to add new features
e.g. phpBB: popular open source product for online forums; modifications built as add-ons for added functionality

20
Q

cost effectiveness

A

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

21
Q

areas of cost-effectiveness

A
  • 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
22
Q

budget for a software project

A

often from the client for whom the project is developed

23
Q

things to think about when formulating budget

A
  • available capital
  • predicted sales for product
  • cost savings as a result of the product
  • ongoing customer support costs
  • other costs
24
Q

what is usually done when large projects go over budget

A

extra funds set aside for unforeseen circumstances, usually 20%