Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Just a question to know how the recruiters think. I know the difference between the "Front-end development" and the "Back-end Development". In a recent application process, the recruiter said that my experience was in "Software Development" but lack of "Back-end Development".
For my understanding and techopedia, back-end development refer to everything that isn't front-end, like database and the logical part of the software/system/application, in an application online or desktop. I even think the Software development may include the front-end part.
Can you explicit say the difference between "Software Development" and "Back-end Development"? With this I can work on my CV that I can let the recruiters know if I'm talking about software development or back-end development.
As a general rule i would say both "Back-end Development" and "Front-End Development" are under "Software Development" Category, So basically both front-end developers and back-end developers can be called software developers.
Front-End Developer: Is someone who primarily works on parts of a software that end user directly interactive with, such as UI of mobile or desktop applications or websites.
Back-End Developer: Is someone who primarily works on parts of a software that end user does not directly interact with, such as database or core logic. Back-End is a more broader term than Front-End.
A software developer who works both on the Back-End and the Fornt-End of a software is usually called a Full Stack Developer, But that's not really universally used term, it's usually a term used within scope of web development.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
Me and my Lab partner are supposed to develop an online shopping website for an imaginary client.
We are also supposed to provide a summary of web development services we are providing to our client.
The question is, what are web development services? Please leave us a simple explanation. Thanks!
Usually most of the web development companies provides different kind of services to their Clients that cater B2B and B2C Customers through Solutions
Some of the example services include
E-Commerce Applications
Educational Applications
Discussion Forums
Single Page Web Applications
Social Networking Sites
Content Management Systems etc.
Above are just some of the many services provided by a web development companies. You can also showcase your skill set and other features saying that
why should a client opt for you.
Try to visit different Web Development companies sites and read the services they provide for better understanding of the kinds of services that are available.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
At the moment we are a small development team of 2. All our software is used inhouse. Currently staff just walk to our desk when they want new software developed or when they want new features added to existing software, or when bugs arise.
I am looking for a better management process of this. Do I get staff to send an email instead and then that can be designated to a developer. Or is there a simple software app out there that could help?
I want a simple method for doing this as the staff are unlikely to use something if too time consuming or complex. They find it too easy to approach a developer personally!
Anything to recommend please?
One option is to use JIRA. It has a feature where emails sent to a certain address can get turned in to backlog items (using the email subject line as the title).
Keep it as it is for now: face-to-face communication is always better than using any piece of software...
It will be only when you will grow to more developers that you will really need such software: from online or cloud based (ie Zimbra) to VCSs (version control systems) hosted on your machines.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
i'm about to start a project for sharing files, announcements, and other stuff between branches of a company, it must be a web based system, with all the layers as profile management, employee communication, etc... What i don't know is what's the name of this kind of systems? It's a web based system wich will only allow access to the company's personnel(still don't know how to do that - help please), and must connect the different branches.
I think you're making an Intranet Software or kind of that.
Look here:
http://en.wikipedia.org/wiki/Enterprise_social_software
Software examples
Specific social software tools which programmers have adapted for enterprise use include:
wikis
social bookmarking
social search
Web Content Management System
instant messaging
file sharing
So, you are doing a profile management, file sharing...it looks like an intranet.
Example of intranet: http://www.intranetdashboard.com/
A textbook name I've met for these type of systems is "Knowledge Management Information Systems".
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
We have a huge debate in our organisation to use AGILE in ERP projects. Can anyone give an example of a successful implementation as such?
Here are some papers and websites that you might be interested in:
Agile Project Management Methods for ERP: How to Apply Agile Processes to Complex COTS Projects and Live to Tell About It
Agile ERP: "You don't know what you've got 'till it's gone!" (Requires IEEE Xplore Subscription or article purchase to view)
Agile Project Management Methods for ERP
Agile ERP
I'm not that familiar with building ERP software, but from what it seems, they appear to have a few things in common. ERP software is large in terms of features and scope and development often takes a long time. I believe that Agile principles might be of value here, even if you aren't using full-blown agile methodologies.
The central tenets of Agile are rapid delivery of working software, accepting late-changing requirements, and close cooperation between the business and users and developers. A highly iterative approach to building an ERP system and close collaboration between the users and the developers to continually add the features that add the most value seem like it will yield the most bang for your buck.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've come across the phrase 'sustaining software engineering' but don't know exactly what it means. There seems to be some DoD connection? Is it related to Agile Development?
Many in the software world define sustaining engineering as the bug fix team. While this is a part of the duties involved the sustaining engineering group should also be looking at the overall defect trends to help identify areas needing re-factoring. The focus of the group should be to not just fix bugs as they come in but to be the conduit back into engineering to ELIMINATE needless calls from customers. That might involve "works as designed" issues as well as product areas the customers just have a hard time understanding.
I believe "sustaining" is another word for "maintenance": it's what happens after software is released, i.e. support, bug fixing, enhancements ...
Sustainable Software Engineering: Consideration of the social and environmental effects of software projects in managing the project. Managing a software project in order to maximize the positive and minimize the negative social and environmental effects of the project.
Alternative (Sustaining): Consideration of the long-term support requirements during the design and development of a software project. The process of conducting the long-term support required when development is complete.
It's just a fancy way of saying "Software Maintenance Team".
Sustaining Software Engineering, at least in the cases where I've come across it, is the department responsible for implementing hot-fixes for released products, and handling customer service issues that the tech-support guys can't resolve on their own.